SQL Accounting
Connect external business systems, automate supported accounting records, and add operational workflows around your existing installation.
- Ecommerce, POS, ERP, and CRM
- Warehouse, payment, and internal systems
SQL Accounting and AutoCount API gateway
Add a secure REST API to your SQL Accounting or AutoCount installation — no VPN, no static IP, no inbound firewall changes required.
For software teams and integration partners across Malaysia, Singapore, and Southeast Asia.
Need a complete integration rather than API access alone? Discuss a custom project →
# SQL Accounting connector
GET /v1/sqlacc/customer-invoice
Authorization: Bearer lb_live_...
# AutoCount connector
GET /v1/autocount/ar/debtors
Authorization: Bearer lb_live_...
200 OK
{
"connection": "company-sqlacc",
"brand": "sql_accounting",
"data": [
{ "doc_no": "INV-00142", "status": "outstanding" }
]
}Why AcctBridge
Building a custom on-premise connector is rarely worth it — weeks of engineering time upfront, then permanent maintenance. AcctBridge handles the access layer so your team doesn't rebuild it for every project.
Accounting software has no REST API out of the box
AcctBridge answer
AcctBridge installs a brand-specific local connector that exposes documented REST endpoints for SQL Accounting and AutoCount — COM BizObjects for SQL Accounting, SQL Server access for AutoCount.
Company networks block inbound connections
AcctBridge answer
The connector uses outbound HTTPS only. No port forwarding, no static IP, no firewall rule changes needed on the accounting machine's network.
Every project rebuilds the same access layer
AcctBridge answer
One portal, one installer, one setup flow. The same pattern — create connection, install connector, verify, call API — repeats for the next branch, company, or accounting instance.
Who sees your financial data when it passes through a cloud gateway?
AcctBridge answer
AcctBridge processes supported accounting request and response bodies in transit without persisting them in the hosted application database or API usage logs. We separately retain the account, connection, and request metadata needed to operate and troubleshoot the service.
Implementation path
Three steps: create an account, install the connector, call the API. SQL Accounting and AutoCount each have their own API prefix, while onboarding, auth, tunnel provisioning, and monitoring stay consistent.
Sign up, select your accounting brand (SQL Accounting or AutoCount), and download the connector package from the portal.
Run the installer on the machine where the accounting software runs. It sets up the local agent and outbound tunnel with guided defaults.
Use the portal connection check to confirm the connector is live, then call the brand-specific API endpoint with your API key.
Integration services
AcctBridge can assess the workflow, build the middleware or application, test the data flow, and help deploy it. Choose the accounting system you already use.
Overview of custom integration servicesConnect external business systems, automate supported accounting records, and add operational workflows around your existing installation.
Build a controlled data flow for retail, sales, warehouse, operations, or finance processes that need to work with AutoCount.
Verifiable before you buy
Use the public product material below to check API coverage, setup requirements, pricing, the accounting data boundary, and the available contact path.
Inspect the OpenAPI documents for SQL Accounting and AutoCount, including published paths and request shapes.
Browse API docsReview the installation path, authentication model, connection check, and first request before you start.
Read Quick StartCompare the 30-day Free evaluation with Launch, Scale, and the written-quote Custom Platform plan.
Compare plansSee which accounting records are processed only in transit, which service data is retained, and how API usage logs are handled.
Review data boundaryUse the public inquiry path for product fit, rollout, installer, tunnel, or API questions.
Contact AcctBridgeExample deployment pattern
A regional software provider may need its WMS, industry platform, or internal application to reach separate SQL Accounting and AutoCount installations. Each installation keeps its own connector, outbound tunnel, and API key boundary.
Upstream software
WMS, industry platform, or internal application using documented brand-specific endpoints.
Connectivity layer
Example installation A
Customer-deployed Windows accounting machine
Dedicated connector · outbound tunnel · separate access boundary
Example installation B
Customer-deployed Windows and SQL Server environment
Dedicated connector · outbound tunnel · separate access boundary
Illustrative architecture — actual setup may vary by customer environment.
The same documented setup can be repeated for another supported installation without opening inbound firewall ports or requiring a static IP address.
Start with 30 days of free access. Paid plans show clear pricing before signup or checkout.
US$0
30-day trial
Test one accounting workflow before paid access.
US$49
per month
For the first managed accounting instance.
First paid month includes 1 extra month of access.
US$199
per month
Billed monthly for multiple accounting instances.
First paid month includes 1 extra month of access.
Written quote
Platform pricing is quoted before rollout.
For more than 5 instances, branches, companies, or partner rollouts.
Public signup starts the first accounting connection for the selected brand. Launch and Scale subscriptions are purchased in the portal through Creem. New paid Launch and Scale customers receive one extra month of access after payment confirmation; the extra access is applied manually and does not change the recurring subscription price. Prices are shown excluding tax; any applicable tax is added at checkout. Prices for all platform plans, including Custom Platform, may change for future purchases and at renewal with prior notice. Custom integration development is a separate project, scoped and quoted after the required workflow is confirmed.
Partner program
We work with SQL Accounting and AutoCount implementers, ISVs, local IT consultants, and reseller partners serving SMEs across Malaysia, Singapore, and Southeast Asia.
Approved partners can refer qualified customers or support multi-company rollouts. Referral and revenue-share terms are agreed in writing before any commercial work begins.
Introduce qualified SQL Accounting or AutoCount integration opportunities from customers who already need a reliable API gateway.
Support rollout planning, agent installation, first workflow validation, and handover for accounting installations.
Coordinate multi-company or multi-branch rollouts with agreed support ownership, commercial terms, and written reseller coverage.
Public partner copy does not create commission, reseller, or revenue-share rights. Commercial terms vary by role, rollout volume, payment method, refund exposure, and support ownership, and must be confirmed in a written agreement.
From the blog
Security
AcctBridge uses an outbound tunnel model so accounting machines do not need inbound firewall rules, static IPs, or public database exposure.
Use case
Use AcctBridge as the API layer for POS, Shopify middleware, ecommerce, OMS, or custom apps that need to write supported accounting records into SQL Accounting or AutoCount.
Security
AcctBridge proxies supported SQL Accounting and AutoCount requests in real time and avoids storing customer financial payloads in the hosted control plane.
Share your accounting system, company or team context, and the first workflow you need to connect.
For installer, tunnel, connection check, or API connection issues, email support@acctbridge.com. We use portal status and diagnostics to help review the next step quickly.
For workflow mapping, rollout questions, or custom integration planning, email hello@acctbridge.com or use this form. We will reply with scope questions and next steps.
For reseller, integrator, referral, or multi-company partnership discussions, contact hello@acctbridge.com. Partner and revenue-share terms must be agreed in writing before commercial work begins.
Create an account, install the matching local agent, and make the first brand-specific API call from your own app.
Account access uses email verification and connector packages generated from your portal.
Need AcctBridge to assess, build, test, and deploy the complete integration? Discuss a custom project →