Which MISA products are supported?

BancoOS supports MISA SME and MISA AMIS through their official APIs, with mapping for vendors, GL accounts, cost centres, projects and Vietnamese tax codes.

Is the integration two-way?

Yes. Master data flows from MISA into BancoOS, and operational data (approved invoices, payments, credit notes) flows from BancoOS back into MISA in near real-time.

How long does a typical MISA integration take to set up?

Most customers complete MISA setup in 2–5 business days: half a day for credentials and mapping, 1–2 days of sample-period validation, and a short parallel-run before go-live.

What happens if MISA is temporarily unreachable?

BancoOS queues sync events and retries with exponential back-off. No data is lost — once MISA is reachable again, the queue drains in order, preserving causal sequence.

Integration · MISA

BancoOS + MISA: setup, data flow and troubleshooting

MISA is the accounting system of record for most Vietnamese businesses. BancoOS sits on top of MISA as the operational layer — capturing invoices, running approvals and pushing posted entries back into MISA without re-keying. This page documents how to connect the two, what syncs in which direction, and how to handle the issues that come up.

Prerequisites

An active MISA SME or MISA AMIS tenant with API access enabled.
A dedicated MISA integration user with permission to read masters and post invoices and payments.
A BancoOS workspace with admin rights to configure integrations.
Network reachability between BancoOS and your MISA endpoint (cloud MISA works out of the box; on-prem MISA may need an outbound API rule).

Step-by-step setup

Create the MISA integration user. In MISA, add a dedicated user with API access. Avoid using a real employee's account so credential rotation does not break the integration.
Connect from BancoOS. Open Integrations → MISA → Connect, enter the MISA API endpoint, tenant identifier and the integration user's credentials. BancoOS validates the connection before saving.
Map masters. Map MISA vendors, chart of accounts, cost centres, projects and Vietnamese tax codes to BancoOS dimensions. Most mappings auto-suggest based on MST and account number.
Run a sample period. Enable parallel posting for one to two weeks. Compare the BancoOS Activity log with MISA postings daily and resolve any exceptions before cutover.
Go live. Switch BancoOS to the operational entry point. MISA remains the system of record; BancoOS handles capture, matching, approvals and payments.

Expected data flows

From	To	Object	Cadence
MISA	BancoOS	Vendors and MST	Hourly + on-demand
MISA	BancoOS	Chart of accounts, cost centres, projects	Daily
MISA	BancoOS	Open purchase orders	Every 15 minutes
BancoOS	MISA	Approved AP invoices	On approval (near real-time)
BancoOS	MISA	Credit notes and adjustments	On approval
BancoOS	MISA	Payment runs and bank confirmations	On settlement

Troubleshooting

Vendor not found when posting an invoice

Likely cause. The supplier MST in BancoOS does not match a vendor record in MISA.

Fix. Open the exception in BancoOS, map the supplier to the correct MISA vendor, then retry the post. New vendors can be auto-created if that option is enabled in workspace settings.

GL account rejected by MISA

Likely cause. An account in the BancoOS code mapping was archived or renumbered in MISA.

Fix. Trigger a chart-of-accounts re-sync from Integrations → MISA → Re-sync masters, then re-apply the mapping in the affected invoice template.

Posting succeeds in BancoOS but invoice is missing from MISA

Likely cause. The MISA API returned an asynchronous error after the initial acknowledgement.

Fix. Check Integrations → MISA → Activity. Failed events show the MISA error code; click Retry once the underlying issue (often a locked period or missing fiscal year) is fixed in MISA.

Tax code mismatch on a sync

Likely cause. Vietnamese VAT codes in MISA do not match the BancoOS tax code mapping.

Fix. Update the mapping in Integrations → MISA → Tax codes. Existing exceptions can be re-posted in bulk once mapping is corrected.

Connection drops with authentication error

Likely cause. MISA API credentials were rotated or the integration user was disabled.

Fix. Re-authenticate from Integrations → MISA → Reconnect. Use a dedicated MISA integration user so day-to-day password changes do not affect the sync.

Frequently asked questions

Which MISA products are supported?: BancoOS supports MISA SME and MISA AMIS through their official APIs, with mapping for vendors, GL accounts, cost centres, projects and Vietnamese tax codes.
Is the integration two-way?: Yes. Master data flows from MISA into BancoOS, and operational data (approved invoices, payments, credit notes) flows from BancoOS back into MISA in near real-time.
How long does a typical MISA integration take to set up?: Most customers complete MISA setup in 2–5 business days: half a day for credentials and mapping, 1–2 days of sample-period validation, and a short parallel-run before go-live.
What happens if MISA is temporarily unreachable?: BancoOS queues sync events and retries with exponential back-off. No data is lost — once MISA is reachable again, the queue drains in order, preserving causal sequence.