Running one outlet, reconciling the till against your books once a month is manageable. Running three, five or more, it turns into a standing task: someone pulling each branch's sales summary, matching it against purchases and procurement, and keying it all into the accounting system by hand, outlet by outlet, month after month. Popcorn POS connects directly to two accounting systems used by Malaysian F&B chains — Million Accounting and AutoCount — so that work happens automatically instead, and it doesn't cost anything extra on top of your existing Popcorn plan. This guide covers how each connection actually works, what gets posted into your books, and what to expect from the setup itself.
Why multi-outlet accounting is a different problem
A single-outlet owner can close the till, check it against a receipt pile, and move on. Add a second outlet and that check has to happen twice, on two separate sets of numbers, often reconciled by two different people with two different habits for how carefully they do it. Add a fifth or eighth outlet and the risk isn't just the time it takes — it's the mismatches that creep in: a branch's procurement figure keyed into the wrong GL account, a sales total entered a week late because that outlet's report arrived late, a payment-type breakdown that doesn't tie out because someone typed it from memory instead of the actual report. None of this is any one person's fault. It's what happens when the same manual step gets repeated across every branch, every closing period, indefinitely.
Two ways Popcorn POS connects to your accounting system
Which one applies to you depends on which accounting software your outlets already run on. The two work quite differently, and it's worth knowing which kind of setup you're actually signing up for.
Million Accounting: a direct database connection
The Million Accounting integration connects Popcorn directly to your own on-premise Million SQL Server database. Setting it up means identifying that server's SQL port, forwarding that port on your router, assigning the server PC a fixed IP address, and creating inbound and outbound Windows Firewall rules for the SQL port. This is network configuration — the kind of task usually handled by whoever manages your IT, rather than something to attempt without support, and it's worth planning for as a real setup step rather than assuming it's a quick toggle.
Once connected, from the Popcorn backend you choose an export period — single transaction, daily transaction, or monthly transaction — map your GL account numbers against payment types and sales categories, then select which outlet, date range and invoices to export, covering sales, purchases and procurement. Each export posts as a proper double-entry directly into Million Accounting, and shows a "SENT" status once it's gone through.
AutoCount: a plugin, no network setup
The AutoCount integration works differently and is considerably lighter to set up. It runs as a plugin installed on the AutoCount side, which then connects directly to Popcorn POS — no router configuration, port forwarding or firewall rules required on your end. For the exact scope of what syncs through the AutoCount plugin and how export periods or GL mapping are handled there, it's worth confirming directly with Popcorn's team for your specific setup, since the two integrations aren't identical under the hood.
| Million Accounting | AutoCount | |
|---|---|---|
| Connection type | Direct on-premise SQL Server connection | Plugin installed on AutoCount, connects directly to Popcorn |
| Setup involves | Port forwarding, fixed server IP, firewall rules (typically an IT task) | Installing the plugin — no router or firewall configuration |
| What posts | Sales, purchases and procurement, GL-mapped, as double-entry, by outlet and date range | Confirm current scope with Popcorn for your setup |
What actually gets posted into your books
For the Million integration specifically, the data that flows across is sales, purchases and procurement, mapped to the correct GL account numbers on both the payment-type side and the sales side. That mapping is what lets an export land as a proper double-entry in Million rather than a raw number someone still has to categorise by hand. You choose the outlet, the date range and which invoices to include before each export, so you retain control over exactly what's being posted and when — this isn't a background sync running without your input.
Why this matters more as you add outlets
Because Million exports are chosen per outlet, per date range, a multi-outlet chain can close one branch's books at a time, or work through all of them on a consistent schedule — daily, or batched monthly — without the figures for each outlet depending on someone remembering to chase down that branch's manager first. The more outlets you run, the more that consistency is worth: two branches with slightly different habits for when and how carefully they reconcile is a minor annoyance, but five or eight branches drifting in different directions is a real risk to the accuracy of your monthly close.
A worked example: closing the books for a three-outlet chain
Picture a three-outlet mamak or café chain on Million Accounting, closing the month manually. Each outlet manager sends a sales summary and a rough purchases figure by WhatsApp, none of it on the same day, and someone — usually the owner or a bookkeeper — spends an evening cross-checking three sets of numbers against receipts before typing them into Million by hand, mapping each transaction to the right GL account as they go. Miss a procurement entry from one branch, or map a payment type slightly differently at outlet two than at outlet one, and the mismatch usually isn't caught until the accountant asks why the numbers don't tie out weeks later. With the integration connected, that same close becomes three exports — one per outlet, for the date range in question — each one posting as GL-mapped double-entry directly into Million, with a "SENT" status confirming it went through. The bookkeeping work hasn't disappeared, but the re-typing and the guesswork around GL mapping has, and it stays consistent whether you're closing three outlets or eight.
Keeping GL mapping consistent matters for compliance too
If your outlets operate under one company registration, LHDN e-Invoice and SST reporting need to tie back to consistent figures branch to branch, not numbers that were categorised differently depending on who did the data entry that month. Posting sales, purchases and procurement into your accounting system with the same GL mapping across every outlet is part of what keeps your books and your compliance reporting in agreement with each other, rather than something you discover doesn't match during an audit.
Which integration applies to you
If your outlets already run on Million Accounting and you have IT support who can handle a port-forwarding and firewall setup, the direct database connection gives you granular, GL-mapped exports by outlet and date range. If you're on AutoCount, the plugin path avoids the network configuration entirely, though it's worth confirming with Popcorn exactly what data it currently syncs for your setup before you commit to a workflow around it. Either way, the underlying goal is the same: sales, purchases and procurement should end up in your books without someone re-typing them from a till printout, one outlet at a time — and either integration is included with your Popcorn plan, with no extra software fee on Popcorn's side for connecting it.
Get it connected before your next closing period
If you're running multiple outlets on Million Accounting or AutoCount and still reconciling branch by branch by hand, talk to Popcorn POS about getting the integration set up — and about IT support for the Million database connection, if that's the piece you're missing.
