Rate and meter
Retain service, client, shipment, handling, accessorial, tariff, quantity, currency, and source operation.
Financial-system integration
Carry operational invoice evidence into accounting.
Available with configuration
XMS Cloud connects logistics billing and invoice status to vendor-specific accounting APIs and file rails. Each connector covers named objects and directions; none should be read as complete ERP implementation.
Operational-to-financial chain
Keep the charge source attached to the accounting document.
Review and invoice
Approve billable usage, tax treatment, customer identity, lines, totals, numbering, documents, and evidence.
Export or post
Use the configured accounting API or file format with idempotent external reference and explicit object scope.
Reconcile
Read accepted, rejected, posted, paid, credited, or failed state where the connector exposes it; retain correction history.
Cataloged accounting paths
Vendor name, protocol, and object scope remain explicit.
Pennylane
REST Company API v2 invoice push and status synchronization through a dedicated client and integration tests.
Cegid Loop
API Publiques invoice export and import-status synchronization; tenant and API entitlement require review.
Sage X3
Sales-invoice integration through SOAP CAdxWebServiceXmlCC; long-running calls use an extended client timeout.
Sage Intacct
XML gateway accounting client; transport retry is constrained because calls may be billable transactions.
MyUnisoft, Sellsy, Axonaut, Qonto, Holded
Vendor-specific REST invoice clients and integration contracts; exact fields and status coverage differ.
Sage 100 PNM, DATEV EXTF, and FEC
Accounting file generation only; no remote delivery, acceptance, or status confirmation is implied.
Control and security
Prevent retries and mapping repairs from becoming duplicate finance.
One external reference
Bind legal entity, customer, invoice number, source invoice, credit note, currency, tax, and provider document id.
Retry by provider semantics
Do not assume an HTTP retry is safe. Persist request, external id, response, status, and reconciliation before resubmission.
Purpose-scoped credential storage
OAuth, dual-key, API-key, Basic, and vendor secrets remain outside normal operator pages and logs.
Invoice is not full ERP
General ledger, master data, bank, purchase, payroll, consolidation, tax filing, and close are separate capabilities unless proven.
Financial operations
Review billed, paid, open, and operational cost together.
Warehouse and transport charges retain source evidence so finance can trace an accounting document back to the activity that created it.
- Billable usage and rate-card provenance.
- Invoice, payment, credit, dispute, and settlement state.
- Client revenue, pass-through cost, and margin context.
Accounting compatibility review
Bring the legal entities, invoice samples, tax rules, provider API, and reconciliation requirements.
Define exact objects, direction, frequency, identity, idempotency, correction, status, security, and ownership.