Build what's next with Remizen.

It is a way for software companies to start a conversation with Remizen about connecting products for shared customers. Remizen is a financial operations platform covering expense management and reimbursements. The program is about exploring software-to-software integrations, product partnerships and technology alliances, not about client implementation services, which is the focus of the system integrator program. Today it begins with an application and a scoping discussion; it is not a self-service enrollment, and applying does not establish a partnership.

Any company that builds software used by finance, HR, operations or accounting teams can apply. Typical applicants are SaaS platforms, fintech providers, accounting and ERP vendors, payroll and HR platforms and enterprise software companies. Remizen reviews each application for fit with shared customers, so it helps to describe the customers you have in common and the workflow problem you want to solve.

Integrations are agreed one at a time. You describe the workflow, we discuss what each side can support, and together we decide on scope, data requirements and the customer experience. Remizen's developer documentation is a planned API reference, so it informs those conversations but is not yet an operational interface. Bring questions about direction of data, who owns the customer relationship, and which records matter.

Remizen publishes documentation at docs.remizen.com, labelled as a planned API for reference only. It outlines design intent using illustrative data. API integrations are not implemented or activated yet, so there are no usable endpoints, credentials, webhooks, SDKs or sandbox environments to start building against. Reading it is useful for preparing technical questions.

The integration directory lists accounting, HR and payroll, productivity, communication, security and other applications, each with a status: Available, Coming Soon (planned, not live) or Contact Us (unverified, discuss first). Check a provider's own page for its status before assuming anything works. Capabilities listed there describe potential connection use cases.

Yes, accounting software companies can apply. The shared customer is usually a finance team that wants approved expenses to reach the books with context intact. Useful scoping questions are which coding fields your ledger requires, how corrections should flow back, and how finance would review records before they are posted. Existing directory entries such as QuickBooks Online and Xero show current status.

ERP providers are welcome to propose integrations. ERP scenarios tend to involve multiple entities, chart-of-accounts structures and close processes, so the first conversation should cover those. Directory entries such as NetSuite and Microsoft Dynamics 365 are marked Contact Us, meaning they should be discussed rather than assumed to be available.

Payroll and HR products appear in the directory with differing statuses, for example ADP as Coming Soon and Workday as Contact Us. Relevant discussion topics include employee records that shape approval routing, and how reimbursement information should be handed to payroll. Nothing about employee provisioning or synchronization should be assumed; those are design topics to scope.

The five stages above outline a proposed process: connect, discover, design, develop and launch. A useful proposal identifies the customer problem, data ownership, required permissions and expected review steps. Production development depends on implemented technical capabilities; the developer portal currently provides reference material only. Timing, resourcing and availability need separate agreement, without guaranteed engineering resources, certification or launch support.

Yes. The application form includes a field for your partnership idea. Describe the systems involved, the workflow, and who the shared customers are. Proposals are reviewed against what Remizen can support, and submission does not commit either side to build anything.

Technology partners are software companies connecting products, so the work is product-level: integrations, alliances and connected experiences. System integrators are service firms who configure and deploy Remizen for client organizations. If you implement software for clients, see the system integrators program; if you build a product customers also use with Remizen, this is the right place.

Select Become a Technology Partner and complete the application with your company details and a short description of the integration or partnership you have in mind. Applications are saved for review, and you receive a reference on submission. Remizen may follow up to discuss fit and next steps. Submission does not establish a partnership or program benefits.