GTreasury to NetSuite

A Boomi integration connecting GTreasury, NetSuite and an SFTP server: journal entries flow into NetSuite, and balances flow back to GTreasury.

The challenge

Treasury and accounting need the same numbers. Journal entries arrive as files, posted transactions live in NetSuite, and the treasury system needs current balances. Keeping all three aligned by hand means exports, uploads and reconciliation every period.

How it works

1. Connect to GTreasury. Set up an HTTP connection to GTreasury using token-based authentication (OAuth 1.0).
2. Journal entries into NetSuite. CSV flat files from SFTP are turned into NetSuite Journal Entries.
3. Balances back to GTreasury. A NetSuite saved search pulls the posted transactions, and the integration creates the matching balances in GTreasury over HTTP.
4. Vendor export. A separate process exports NetSuite vendors to the local system as an XML file.
5. On-premise runtime. A local Boomi Atom was installed on a local machine to deploy and run the processes.

Highlights

• Two-way flow: files into NetSuite, balances out to GTreasury.
• OAuth 1.0 token-based HTTP authentication.
• Saved-search-driven export keeps the selection logic inside NetSuite.
• Runs on a locally installed Boomi Atom.

The result

Treasury balances and the general ledger stay aligned without manual exports, and file-based entries post to NetSuite automatically.

At a glance