Finance professional reviewing financial reports on a laptop and monitor in an office overlooking a warehouse floor

Trust Is Built in the Data Model: Master Data, Transactions and the Ledger

What a CFO should look for beneath the screens of any ERP

Ask a CFO what they want from an ERP and the answer is usually simple: numbers I can trust, without a week of reconciliation. That trust is not created in the reporting layer. It is created much deeper, in how the system separates three kinds of data that are easy to blur together, and in how it controls who can change them.

Layer 1: Master data, the rules of the business

Master data defines the things your business deals with: customers, vendors, items, bills of materials, price lists, warehouses and the chart of accounts. It changes slowly, and every transaction depends on it.

Because so much depends on it, master data needs governance. A changed payment term on a vendor, a new unit of measure on an item or a remapped GL account affects every transaction that follows. The questions that matter are who can make those changes, whether the change is approved, and whether there is a record of what changed and when.

Layer 2: Transactional data, the work of the business

Transactions record what happened: a sales order, a purchase order, a receipt, a production completion, a shipment, an invoice, a payment. Each one references master data and moves through statuses.

Well-designed transactional data has two properties. Every transaction is tied to its source, so a shipment points to its order and an invoice points to its shipment. And once a transaction is complete, it is protected. A received purchase order should not quietly change quantity after the inventory has been counted and costed.

Layer 3: Ledger entries, the financial truth

Ledger entries are the accounting consequence of transactions. A receipt debits inventory and credits accrued payables. A shipment relieves inventory and records cost of goods sold. An invoice records revenue and a receivable.

Three principles separate a trustworthy ledger from a fragile one:

  • Entries are generated by the transaction, not re-keyed. Operations and finance work from the same event, so the subledger and the general ledger agree by design.
  • Posted entries cannot be deleted. To correct one, it must be unposted first, a deliberate step rather than a quiet edit.
  • Every balance drills back to its source. A CFO or auditor can move from a GL balance to the journal entry to the receipt, order or invoice that created it.

Every balance traces back

Inventory balance
Journal entry
PO-04417

When these principles hold, month-end close becomes a review rather than a reconstruction.

Where GoldFinch is different: cost and timing

Two questions decide whether a CFO trusts the numbers on any given day: is inventory valued correctly right now, and can I see the financial position without waiting for close?

Real-time inventory costing, FIFO or standard. GoldFinch values inventory as each transaction happens, using first-in, first-out (FIFO) or standard cost. With FIFO, cost of goods sold reflects the actual cost layers a shipment consumed, so margin on an order is the margin you actually earned. Manufacturers that prefer standard cost can run it instead, and inventory is still valued as transactions post rather than adjusted at period end.

Financial statements without closing the period. GoldFinch Accounting produces a balance sheet and P&L for an open period. You can review the month as it unfolds, spot a problem in week two, and arrive at close already knowing the answer.

When can you see your P&L?

Week 1Week 2Week 3Week 4Close After close only GoldFinch

One data model for operations and finance. With GoldFinch ERP and GoldFinch Accounting together, the receipt, the inventory movement and the journal entry live in the same Salesforce database.

Security across all three layers

Data integrity depends on access control. An ERP built natively on the Salesforce Platform inherits the platform’s mature security model rather than inventing its own.

  • Profiles and permission sets control which records each user can see and change.
  • Field-level security can hide cost, margin or bank details from users who do not need them.
  • Sharing rules can restrict records by business unit, entity or warehouse.
  • Field history tracking records who changed key fields, and when.
  • Multi-factor authentication protects the front door.

Together these let you configure real segregation of duties. You can set the system so the person who creates a vendor cannot approve its payment, and the person who receives goods cannot post the invoice.

The questions to ask any vendor

  1. How is master data governed, and is there a history of changes to critical fields?
  2. Can a completed transaction be edited, and if so, by whom and with what record?
  3. Are ledger entries generated automatically from transactions, and what does it take to change a posted entry?
  4. Is inventory costed in real time, or adjusted at period end?
  5. Can we see a balance sheet and P&L before the period is closed?
  6. How does your security model enforce segregation of duties?

The bottom line

Trustworthy numbers are not a reporting feature. They are the result of clean master data, protected transactions, a disciplined ledger, costing that keeps pace with operations, and a security model that ties it all together.

Designing that foundation takes a team that understands the platform, the accounting and the industry at once. In the final post, we look at what goes wrong when any one of those three is missing, and why the gaps usually surface after go-live.

GoldFinch builds ERP and accounting on one Salesforce data model, so operations and finance work from the same transactions. If you would like to review your current close process with us, we are glad to help.

Scroll to Top