Heavy daily coin buying, buybacks, and reconciliation. Excel and screenshots couldn't hold it — an operations ERP for a game currency dealer
A game currency dealer handled a high daily volume of coin purchases and buybacks with Excel, screenshots, and manual reconciliation. Shift handovers often didn't balance. We built an operations ERP: orders, reconciliation, shift handover, matching, and invoicing all on one ledger.
- Client
- A Game Currency Dealer
- Industry
- Other
- Service
- AI ERP
- Led by
- Johnny Yang

What we delivered.
- Acceptance items
- 26 items, accepted one by one per contract
- Phase one
- Live in about one and a half months, switched to full operation
- Reconciliation
- Online banking statement import + dual-ledger cross-check + three-layer verification
- Deliverables
- Operation manuals for every role + technical documentation
01One ledger, three people, three checks, still not balancing
The client is a game currency dealer. Players buy game coins by bank transfer or by paying at a convenience store, and they can sell back coins they don't need. Order volume is high, amounts are small and scattered, and the business ran on Excel, chat screenshots, and staff memory.
The worst part was reconciliation. Money coming into the bank, coins going out, and the company's own books often didn't match across all three. At shift change, nobody could clearly explain the gap the previous shift left behind. In a money business, books that don't balance are a risk.
02Why we call it an ERP
This case looks like "game coins". Underneath, it is the same as any trading company: purchasing, shipping, receiving payment, making payment, inventory, reconciliation, handover. Just faster, with smaller amounts, and mistakes show up immediately.
03What we built
Phase one: orders and reconciliation (16 acceptance items)
- Members and blacklist: The same person uses different nicknames in different games. The system ties them to one member. Problem accounts go on a blacklist, and the system warns staff when an order is created. Historical data was imported in bulk.
- Three order types: Coin purchase by bank transfer, coin purchase at a convenience store, and buyback (player sells coins back). Each has its own flow and checks.
- Screenshot recognition assist: When a player sends a payment screenshot, the system reads out the key fields. Staff only need to verify.
- Online banking statement import and matching: Import the bank statement, and it is matched to orders automatically. Anything that doesn't match becomes a discrepancy ticket.
- Dual-ledger cross-check: The operations ledger and the company's own ledger are kept separately and checked against each other. Every gap gets a ticket to track it.
- Shift handover with three-layer checks: Check every transaction, a reminder every N transactions, a full check at handover. A gap cannot be carried into the next shift.
- Permissions, approvals, and audit logs: Who can do what is clearly defined. Every change leaves a trail. Important actions need manager approval.
Phase two: matching and invoicing (8 acceptance items)
- Buy/sell matching: Purchase and buyback orders are paired by rule (one-to-one or one-to-many), matched automatically on a schedule, and carried over across periods.
- Invoice data: Matching results directly generate the data needed to issue invoices (Taiwan's government-format uniform invoices).
- Serial-code inventory and giveaways: Inventory management for serial-code products. When a threshold is reached, a giveaway is issued automatically and recorded on the member's history.
04How we work
This project moved through the contract's 26 acceptance items one by one. At the kickoff meeting we confirmed 24 open questions one at a time. We delivered a clickable prototype for walkthrough first, then a staging site, training, parallel running of old and new systems, and finally picked a day to switch over for real.
After the switch, every round of client feedback went live within a few days. For example: brackets in a player's nickname being misread as a new member, or a player paying first and leaving the coins on hold instead of collecting them. These real-world cases all became formal system flows. Even the old books were cleaned up with reversing entries, not by editing the numbers directly.
05Why the client is not named
This is the core of the client's operations. We only share the approach.
06My take
Whether you sell game coins, parts, or food ingredients, if you have a high volume of small transactions in and out every day, books that balance don't come from more careful staff. They come from a ledger the system guards for you.

