Integrations

Inbound connections

• Employee directory. Inbound directory updates supply identities, departments and manager relationships.
• Corporate-card feed. Supplies posted issuer transactions under stable provider identities.
• Receipt OCR. Inbound extraction results suggest merchant, date and amount while retaining the original evidence for review.
• Maps and travel rates. Inbound reviewed references support journey calculations under the company’s chosen policy.

Outbound connections

• Finance accounting. Outbound approved cost and payable requests follow the agreed posting owner. Confirmed ledger results are received with their source identity.
• Payroll and accounts payable. Outbound employee payment requests follow the selected channel. Confirmed payment and return results are received against Reimbursements. AP separately settles approved CardReconciliations without another expense debit.
• Project and document services. Project codes are validated against the source project. Outbound costing context and documents retain original record references and permissions; this system does not create another client billing owner.

Confirm the result

Agree the cost-recognition owner before connecting AP: do not post the same expense through both a journal and a bill. Preserve one payment channel and stable source identity per approved claim. An accepted request or closed payroll run is not payment confirmation. Test duplicate callbacks, rejected requests, returned payments and reconciliation before the pilot expands.

Configure before launch

The specification identifies the intended contracts. Confirm availability, credentials and supported operations for each chosen connector during implementation; this website is not evidence that a provider is already connected.