Jakarta, UTC+7Open to remote roles and projects

Work/ 02

NetSuite Integration

@Rukita

Financial records now flow from our internal platform to NetSuite on their own, instead of being matched by hand every day.

ROLE
Product Manager
SCOPE
API contract, sync rules, error alerting, launch monitoring
WORKED WITH
Backend Engineers, NetSuite Engineers, Finance
YEAR
2024 to 2025

Problem

Every day, Finance exported about 1,000 records from our internal platform, matched them line by line against NetSuite, fixed every mismatch and imported the corrected data back. The two systems stored financial data in different structures, so they couldn't sync directly. Finance had become the translation layer, and reporting often waited on it.

Why this approach

The mismatch came from how the two systems structured data, so I fixed it where it started: an API integration with the internal platform as the single source of truth.

What I did

I defined the API contract with the backend and NetSuite engineers for invoices, orders, rooms, properties, tenants and landlords: every field, what syncs and what doesn't, which system holds the truth, and the data shape each side needed. I also designed the sync timing, the error behavior and the monitoring plan.

What I built

before

  1. Internal platform
  2. Finance exports, matches, fixes and imports, every daythe daily manual grind
  3. NetSuite

after

  1. Internal platform
  2. API integrationabout 80% less manual work
  3. NetSuite
  4. Alerts go to the right engineer

The call I made

Two calls.

First, I pushed for one source of truth: our internal platform, with NetSuite only receiving. The CTO signed off, and it settled a dispute that had held the project up.

Second, I launched on a longer sync interval on purpose, so problems surfaced before they compounded. I shortened it to near real-time only after the system proved stable.

What could break, and how I tested it

Failed or mismatched syncs piling up unnoticed.

Alerts went by failure type straight to the backend or NetSuite engineer, and Finance was pulled in only when a number needed a business decision.

For three weeks after launch I watched every alert myself, triaged it, confirmed the fix, and decided when it was stable enough to shorten the interval.

Result

When I interviewed the Finance team three months after release, they reported about 80% less manual reconciliation work, and their reporting started landing on time more often.

What I'd change

Settle the source of truth before field work starts.

Whether NetSuite should follow our backend data or the other way round stayed open longer than it should have. Next time I'd get that decided and written down at kickoff, with Finance and both engineering sides in the room.

Close the access gap early.

PMs had no access to NetSuite, so Finance's needs reached our data structure through someone else's translation. I'd ask for read access or a shared field map from day one, so I could check the translation myself.

Building something complex, got a messy workflow or an AI idea?

let's talk!
© Mega SetiawatiBuilt with a little magicSide work: Offscreen