Systemglue Banking · for Oracle NetSuite
Your bank and NetSuite,
reconciled without you.
Outgoing payments leave NetSuite as proper bank files. Incoming transactions come back and match themselves against open invoices — including collective payments. Nobody opens the bank portal to copy numbers again.
What it takes off your desk
Outgoing payments
Vendor bills paid straight from NetSuite
Approved payment runs turn into ISO 20022 files and go to the bank on schedule. Status comes back into NetSuite — you see what was paid, when, and what the bank rejected.
Incoming reconciliation
Customer payments matched to open invoices
Daily account statements are read, matched on reference and amount, and applied. What doesn't match cleanly is left in a short list for a person — instead of the whole day's work.
Balances & cash position
Bank balances visible in NetSuite each morning
Account balances and cleared transactions land in NetSuite automatically, so month-end reconciliation starts from a bank ledger that is already up to date.
What the service includes
Systemglue Banking handles a company's payment traffic between its bank and Oracle NetSuite. Bank transactions are fetched from the bank automatically, matched to open invoices and recorded in NetSuite as payments. Payments go the other way — out of NetSuite to the bank on their due dates — and their status comes back onto the payment record.
The aim is that the account statement and the NetSuite ledger show the same thing on the same day. Most transactions post without anyone touching them, and what is left to sort out is only the part that cannot be identified unambiguously. For those cases a processing view is embedded in NetSuite, where a transaction is matched in a few clicks — no separate banking software and no moving files around.
The service runs on the Systemglue integration platform, so bank connections, certificates and their renewal are our responsibility.
Bank connections
Ready connections to OP, Danske Bank, Rabobank and Qonto. Danske Bank has a file transfer channel (Web Services) alongside the API connection, so no separate bank communications software is needed. Connections are per account, so only the accounts you want are included.
Fetching bank transactions
Transactions and balances are fetched from the bank on an agreed schedule. Every transaction gets its own record in NetSuite, and the bank's original data is kept as it came for traceability.
Automatic matching
Transactions are identified by reference number, message, counterparty name and amount, and matched to open customer invoices, vendor bills or expense reports. Unambiguous cases post themselves as a customer payment, a bill payment, an expense report payment or a journal entry. Partial payments, overpayments and collective payments covering several invoices are each recognised as their own case. Matching rules are tuned per customer.
A processing view in NetSuite
Transactions that were not identified are listed in a view of their own, where the user picks the counterparty and the match and posts the transaction. One transaction can be split across several postings, and the lines are checked against the totals before approval. The view is part of NetSuite, so there are no extra logins or interfaces.
Outgoing payments
Payments are built from vendor bills in NetSuite: the view proposes the bills to pay, calculates cash discounts and fills in the vendor's bank details. Payments are checked before sending and held until the due date, after which they go to the bank either one at a time or as a batch.
Payment tracking
The status of sent payments updates from the bank back onto the NetSuite payment record. Rejected and failed payments appear in a view of their own with the reason given, and can be corrected and sent again.
Account balances
Bank account balances are fetched along with the transactions and shown in the processing view, so the state of the account is visible in the same place as the transactions being reconciled.
Currencies and group structure
The service supports several currencies and foreign-currency matching with exchange-rate calculation, as well as several NetSuite subsidiaries with bank accounts of their own.
Standards
Connections are based on the banks' own APIs and on the ISO 20022 standard (camt.053, camt.054, pain.001, pain.002). Traffic is encrypted and certificate-based.
How it gets in place
One meeting
Which bank, which accounts, which NetSuite subsidiaries. We tell you what the bank agreement needs.
We connect and test
Connector, your matching rules, your custom fields. Tested against real statements before anything goes live.
It runs, we watch it
Failed files and bank outages surface to our team.
What it costs
1 · Implementation — one-time
140€/hour
Meetings, setup, your matching rules and custom fields, testing. With the ready connector the effort is small and known — we estimate it with you and you get a fixed price for the delivery before work starts.
2 · Platform — monthly
from 300€/month
Keeps the integration live, maintained and watched. Covers your first 50,000 integration events per month; each additional 50,000 adds 100€/month.
Which bank are you on?
Tell us your bank and roughly how many transactions a month. We'll come back with an offer or a couple of sharp questions. Not a sales cycle.