Connecting VynSales with AutoCount and SQL Accounting
Most Malaysian SMEs already run their books on AutoCount or SQL Accounting. VynSales is built to sit in front of those systems as your sales engine — handling quotations, orders, invoices, and payments — and to pass the resulting documents through to your accounts without double entry.
API-first, not a closed box
VynSales exposes a REST API at /api/v1 and a webhook dispatcher. Every key document — invoice issued, payment received, order created — can fire an event your integration listens for. That means an AutoCount or SQL Accounting connector can pull or receive sales documents as they happen, rather than someone retyping them at month-end.
What flows across
- Customers — stable IDs so records map cleanly between systems.
- Invoices — header plus line-item snapshots, with unit of measure and tax-ready fields.
- Payments — settlement events with the invoice they apply to.
Because each VynSales document stores a snapshot of its line items, what your accounts receive matches exactly what the customer was billed.
Webhooks you can rely on
Each webhook payload carries a stable event_id (also sent as a header and bound into the signature) so your connector can dedupe safely and retry without creating duplicates. Events include created, updated, issued, paid, and voided.
Where to start
- Generate an API key in Settings → Integrations (Pro and above).
- Subscribe a webhook endpoint to the events you care about.
- Map VynSales customer and item IDs to your accounting system.
Want help scoping an AutoCount or SQL Accounting integration for your team? Talk to us or start a free trial.