We're building custom reporting directly against NetSuite Analytics Warehouse (NSAW) fact tables and reconciling COGS figures back to native NetSuite GL reports (Account 4001 – Cost of Goods Sold, Subsidiary Context = Consolidated, Primary Accounting Book).
On multiple Item Fulfillment transactions, we're seeing a small but consistent overstatement in the raw debit amount compared to what's actually posted to GL:
Document | Raw DEBIT (fact table) | GL posted amount | Ratio |
|---|
ABC | 46,520.55806363013 | 46,514.98 | 1.000120 |
GHI (2 lines summed) | 23,365.70927... | 23,362.91 | 1.000120 |
The ratio is essentially identical (~1.00012x) across different items, different documents, same day/location. This doesn't look like random rounding noise — it looks systematic.
We suspect this may be related to NetSuite's documented GL Impact rounding-adjustment behavior for multi-currency postings, where the system auto-adjusts one line (e.g., the largest-magnitude line) to force debits and credits to balance after currency conversion. Our questions:
- Does this same rounding-adjustment mechanism apply to Item Fulfillment / COGS postings, not just Journal Entries? The documentation we found only describes it for JEs.
- Which underlying table/field, if any, reflects the post-adjustment (final GL-posted) amount at the line level — rather than the raw pre-adjustment calculated debit? We've checked
DEBIT, BASE_EXCHANGERATE, and ACCOUNTINGBOOK_DEBIT on the item fulfillment line table, and none of them tie exactly to the GL-posted figure. - Is this a known, expected variance between NSAW's replicated fact-table amount and the GL report, or does it indicate something in our replication/query logic we should be correcting instead?
Any insight — from Oracle support, NSAW documentation, or others who've hit this reconciling NSAW to GL — would be very helpful. Happy to share more transaction detail if useful.