AutoCount API integration is the practice of connecting external systems—ecommerce stores, POS, CRM, custom portals, or middleware—to AutoCount so master data and transactional documents can move without rekeying. The API exposes programmatic ways to create or update records according to AutoCount’s data rules and your company database configuration.
Integration quality depends as much on accounting design (debtors, items, tax codes, document types) as on code. A perfect connector cannot fix unstable SKUs or unclear document policies.
What teams typically synchronise
- Customers / debtors and, where relevant, creditors
- Items, pricing, and stock-related fields
- Sales documents (invoices, cash sales, orders—based on scope)
- Payments and credit notes when in scope
- Status feedback so the source system knows what posted
AutoCount API integration flow
- External system captures a business event
- Middleware or connector authenticates to AutoCount
- Payload is mapped to AutoCount fields and codes
- API creates or updates the target document
- Result codes are logged and reconciled
Direct connector vs middleware
A single-store sync might use a focused connector. Multi-channel retail, enrichment rules, or multi-company routing often benefit from middleware. See the general pattern in accounting software integration.
Controls that protect the ledger
- Idempotent posting keys to prevent duplicates
- Explicit data mapping owned by finance
- Sandbox or staging proof before production cutover
- Exception queues for tax/item mismatches
- Clear document numbering and audit trails
- Named owner for failed posts during peak seasons
Prerequisites before coding
- Stable item and debtor codes
- Documented tax settings
- Agreement on which AutoCount document types will be used
- Backup and restore plan for the company database
- A non-production database for tests whenever feasible
- Written rules for cancellations, partial shipments, and refunds
Error handling patterns
Map AutoCount validation errors to human-readable exception reasons (“unknown item code”, “credit limit”). Surface them to operations users who can fix master data—not only in developer logs. An exception that only developers can decode will sit until month-end.
Ecommerce and POS nuances
Stock reservations, cancelled orders, and partial refunds need explicit rules. Counter tenders and online payment methods must map cleanly. Read related guidance on connecting AutoCount to ecommerce or POS, and prove those cases in UAT—not only a single successful invoice create.
Multi-company and branch realities
If you run multiple companies or branches, decide how credentials, document series, and warehouses are scoped. Mixing companies in one connector without isolation is an operational and audit risk. Hub designs often encode company routing as configuration.
A concrete path
An online order is paid. Middleware authenticates to AutoCount, ensures the debtor and items exist (or creates them under approved rules), posts the sales document with mapped tax codes, then writes the AutoCount document number back to the store order. If an item is missing, the order lands in quarantine; warehouse fulfilment can still proceed only according to your agreed policy for blocked posts.
FAQ
Can we sync historical invoices in bulk?
Sometimes, but treat historical backfill as a separate project with throttling and validation. Do not casually replay years of documents into production without finance approval.
Do we need middleware for one Shopify store?
Not always. A focused connector can work for a simple one-way post. Add a hub when channels multiply, enrichment rules grow, or you need one operations view across flows.
What should finance prepare before kickoff?
Item list with stable codes, tax code list, sample invoices (including refunds), debtor coding rules, and which AutoCount document types are in scope for MVP.
How do we prevent duplicate invoices?
Use idempotency keys or natural keys (channel order ID stored and checked before create). Test deliberate double-delivery in staging before go-live.
Who owns mapping after go-live?
Finance for tax, GL-related, and document-type rules; operations for fulfilment-related codes. Engineering implements—business approves.
Related concepts
General pattern: how accounting software integration works. Counters: how POS to accounting integration works. Field rules: what is data mapping. Hub choice: what is middleware.