Connected to your stack, accountable to your ledger.
DocQex connects to accounting, identity, HRIS, card, banking, and collaboration systems through replaceable adapters — each with explicit source-of-truth rules, so a sync never silently overwrites a finalized record.
Accounting & ERP
Configurable mappings to your chart of accounts and dimensions, with batch totals, rejected-row handling, retries, and reversals.
Identity & SSO
OIDC and SAML federation through your identity provider, with MFA enforced for privileged and finance-release roles.
HRIS & provisioning
SCIM and HRIS sync keep employees, managers, departments, and cost centers current — joiners, movers, and leavers included.
Corporate cards
Daily card feeds and statement imports, matched automatically to receipts and expenses with feed-health monitoring.
Banking & payroll
Payment files out and payment results back, with payroll handoff for reimbursements where your policy prefers it.
Documents & email
Forward receipts and bills by email, extract their contents, and keep every file scanned and linked as evidence.
Collaboration
Approval requests and reminders where your team already works, always linking back to the governed record.
API & webhooks
A versioned OpenAPI REST interface with idempotency, signed and replay-protected webhooks, and dry-run imports.
Connector availability varies by edition and region. Product names are trademarks of their respective owners.
Exports that reconcile themselves.
Every batch carries source totals, accepted totals, rejected rows, and retry history. Exported records lock; corrections flow as linked adjustments or reversals — so your ledger and DocQex always agree.
- Effective-dated mappings to accounts and dimensions
- Idempotent batches — a retry never posts twice
- Closed-period rules redirect late spend with approval
- Source total
- $486,214.90
- Accepted
- $484,902.15
- Rejected
- $1,312.75
- 214 lines exported212 accepted
- 2 rejected · inactive cost center CC-7300 Retry queued
An API built for money that must not move twice.
Tenant context always comes from the trusted host and credentials — never from the payload. Everything that changes money is idempotent and safe to retry.
# Submit an expense report — safe to retry
POST https://acme.docqex.com/api/v1/expense-reports/RPT-26-0318/submit
Authorization: Bearer ••••••••
Idempotency-Key: 7f3c2a90-61e4-4b8e-9d1f-0c2b5e7a4d11
If-Match: "v12"
# 202 Accepted
{
"status": "submitted",
"policy": { "set": "travel-v4", "result": "within_policy" },
"total": { "amount": "8420.15", "currency": "USD" }
}- Versioned OpenAPI interface with consistent errors and pagination
- Idempotency keys on create, submit, approve, payment, and import
- Optimistic concurrency so no one silently overwrites a colleague
- Signed, replay-protected, retryable webhooks per tenant
- Dry-run imports with row-level outcome files
- Scoped, rotating API credentials bound to one tenant
Tell us your stack. We’ll map the flow.
Bring your accounting system, identity provider, and card programs — we’ll walk through mappings, sync rules, and reconciliation for your setup.
- 45 minutesTailored to your workflows
- Product specialistsNo scripted sales pitch
- Security review readyArchitecture and controls pack