Your banks, inside your ERP — without building a thing.
We wire all your banks into NetSuite, Microsoft Business Central or your TMS — automated bank feeds, vendor bill pay and reconciliation through one secure connection. We build it, run it, and manage every bank for you, so your finance team stops logging into bank portals.
Your ERP still can't talk to your banks
Manual statement uploads
Log into each portal, re-key into NetSuite, every day, per bank.
Reconciliation eats the close
The same transaction in six formats across ten banks; month-end overtime.
Editable files are a control gap
Portal entries and CSV uploads mean fraud risk and audit findings.
We build it
Study the docs, wire into your ERP via plug-and-play NetSuite / Business Central modules.
We run it
Spec changes, ISO 20022 / CBPR+ migrations are our job, not yours.
You keep custody
API-only data flows, no editable files. We move data, never funds.
Use cases
Automated bank feeds
Statements + real-time notifications into the ERP.
Vendor bill pay
Push single or bulk instructions from NetSuite / BC, your approval workflows.
Multi-bank / multi-entity
Reconciliation
Match the moment funds land — audit trail, not a spreadsheet.
FX & balances
Two ways to connect
ERP connectors (no code)
Connect via NetSuite or Business Central app. Acme is the only proper bank-connectivity layer for NetSuite in Singapore,
via our SI partner Lancia Consult.
REST API
For teams building in their own stack or TMS (Kyriba, GTreasury, SAP).
API-only flows your auditors will like
Data onlyWhy Acme
End-to-end delivery
We build it, run it, and own the bank relationship.
Live in 6–8 weeks
Not months.
Maintenance is the moat
We absorb every bank change.
One connection, every bank.
You keep custody
Non-regulated tech layer.
The only proper NetSuite bank-connectivity layer in Singapore.
Acme and Lancia Consult are partnering to deliver complete NetSuite solutions for corporates. Lancia implements and configures NetSuite for your business; Acme connects it to your banks, with automated bank feeds, bill payments and reconciliation built, run and maintained by Acme. One team for your ERP, one for your bank connectivity, delivered as a single project.
FAQ
Does Acme replace our ERP or treasury system?
No. Acme sits underneath your ERP or TMS and connects it to your banks. Your finance team keeps working in NetSuite or Microsoft Business Central using Acme's connectors for bank feeds and bill payments, or your developers can connect any other system to Acme's REST API. Acme handles the bank side: scoping, bank onboarding, testing, go-live and ongoing maintenance. Your bank accounts, relationships and funds stay with you, because Acme never holds money.
Which ERPs and banks can we connect?
Acme offers connectors for Oracle NetSuite (SuiteApp and bundles) and Microsoft Business Central, and a REST API for other ERPs and treasury systems. Acme is the only NetSuite bank-connectivity layer in Singapore, delivered with SI partner Lancia. On the bank side, Acme connects to DBS, OCBC, UOB, HSBC, Standard Chartered, Citibank and others, across 25 banks in total. Supported workflows vary by bank, so we confirm them for your accounts during scoping.
What will the connector actually do inside NetSuite or Business Central?
It brings bank data in and pushes payments out. Daily bank statements flow into the ERP for automated import and matching, and real-time credit notifications show incoming funds where your bank provides them. Approved vendor bills become payment instructions to your bank, sent straight through or via your bank portal's approval workflow. A daily FX rates feed can also go into the ERP, and all your connected banks and entities appear in one place.
How long does implementation take?
Typically 6–8 weeks, compared with the 9–12 months a traditional multi-party ERP-to-bank project can take. Acme leads project management and the bank-side implementation, covering scoping, bank onboarding, testing and go-live, so your finance team isn't chasing several stakeholders. Bank-side onboarding varies by bank and can affect the timeline. Once live, adding another bank or entity follows the same process and connector.
Is this more secure than uploading payment files to a bank portal?
Yes, because there are no editable files in the flow. Payment instructions and statements move by API between your ERP, Acme and the bank, so nobody can alter a CSV between export and upload, a common route for fraud and compliance gaps. Acme stores bank credentials PGP-encrypted, encrypts data with AES-256 on AWS in Singapore, lets you restrict API keys to your IP addresses, and is ISO 27001:2022 certified.
Who handles bank format changes and the ISO 20022 migration?
Acme does. We maintain each bank connection, including file and API version upgrades and the ISO 20022 (CBPR+) changes, including SWIFT's November 2026 requirements for structured address data. Where a bank needs new information, such as fuller beneficiary addresses, we publish the change in our changelog in advance so you can update vendor records. We also shielded a client through Standard Chartered's core-banking upgrade.