These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Apparel & Footwear ERP
- Features
- Entities and master data
Entities and master data
Give each department the same approved reference data while keeping legal entities and sensitive information distinct. This module defines the currencies, calendars, accounts and authorities that every commercial and operating transaction must follow.
OverviewMy Approvals×
Apparel & Footwear ERP · Entities and master data
New
My Approvals
Approvals
| Approval number | Document type | Document ID | Entity | Step | Amount | |
|---|---|---|---|---|---|---|
| APP-98631 | Requisition | PO-2026-0882 | Harbor Thread Logistics Ltd. | 80 | 30,312.93 | |
| APP-61008 | Purchase order | BILL-2026-0614 | Harbor Thread Europe BV | 590 | 28,504.86 | |
| APP-87587 | Bill | SO-2026-0841 | Harbor Thread Sourcing Ltd. | 370 | 14,778.75 | |
| APP-67579 | Payment run | WO-2026-0317 | Harbor Thread Sourcing Ltd. | 470 | 32,290.14 | |
| APP-58898 | Sales order | JE-2026-0209 | Harbor Thread Europe BV | 40 | 11,789.09 |
6 of 6 records
PO-2026-0882Approvals · APP-98631
RequisitionEntityHarbor Thread Logistics Ltd.
Step80
Amount30,312.93
Limit appliedUSD 5,000 buyer limit
Delegate forTheo Laurent
What you can do
Keep style identity separate from the SKU
Maintain style, color, size and season labels on the approved product record. Staff can read an assortment without treating every size as interchangeable stock. A new season does not automatically create a new stock balance or change the carrying value of earlier goods.
Organize the legal entities
Each entity identifies its functional currency, local calendar, tax registration, parent and reporting relationship. A document belongs to one entity’s ledger and must use compatible accounts, periods, warehouses and counterparties. An intercompany partner is identified explicitly rather than inferred from similar account names.
Ownership percentages and consolidation methods have an effective basis. Historical reporting retains the included entities and ownership used for that pack; changing today’s structure cannot rewrite a previously locked consolidation.
Cost centres provide management reporting within the entity. Departments organize positions and employees, and their defaults help route a charge. A line can carry its actual cost centre rather than inheriting a header default that hides where the work occurred.
Keep currencies and dates explainable
Currencies retain their decimal precision. Exchange-rate records identify the currency pair, date, type and source. Transactions, settlements, revaluation, budgets and consolidation use the appropriate captured basis; a missing rate or ambiguous conversion requires resolution.
Document date describes the business document. Posting date determines the ledger period and must fall within a valid period for the same entity. Open periods accept eligible normal postings. Soft close permits only authorized adjustment scope, and hard close prevents new posting into the locked period.
A late supplier document keeps its original date. An explicitly authorized next-open-period posting uses its own posting date and explanation; it is not silently redated to make the entry succeed.
Define how an event reaches the ledger
| Reference data | What it controls |
|---|---|
| Chart of accounts | Account hierarchy, normal balance, control-account and intercompany rules |
| Posting mappings | The inventory, WIP, revenue, expense, accrual, tax and variance accounts for the actual event |
| Payment terms | Due dates and eligible early-payment discount conditions |
| Tax configuration | Effective jurisdiction, direction, additive tax, withholding and recoverable treatment |
| Bank configuration | Entity, currency, ledger account and authorized instruction format |
A control-account flag is not enough to choose the correct posting. Explicit mappings identify the account for each source and treatment. Subledger journals carry that evidence; broad master-data access does not authorize arbitrary manual entries into control balances.
Tax defaults help select a candidate treatment. Final tax still needs the actual product, counterparty, jurisdiction, date and exemption evidence. Withholding is separate from additive sales or purchase tax, and recoverable versus non-recoverable tax follows its configured expense, asset or liability treatment.
Maintain customer and vendor identities
Accounts can be customers, vendors or both, with distinct commercial terms on each side. Contact persons retain their relationship, owner and activity history. Sales Manager and Buyer maintain their authorized commercial scope without gaining bank-change authority.
Duplicate review uses the actual identifiers and retained source history. A controlled merge preserves document relationships; a similar display name is not sufficient evidence that two counterparties are the same legal party.
Vendor banking changes follow a reviewed old-to-new change with actual actors and evidence. Company bank access and employee bank access follow different field policies. Payroll instruction generation receives only the details authorized for that task, rather than unrestricted account access.
Record the person behind each decision
Employees identify authenticated users, assigned roles and limits for specific document types. Approval captures the submitted revision, applicable policy, amount, currency, limit and actual signer. A numeric limit does not grant an action that the person’s role is prohibited from performing.
Delegation identifies the principal and the actual delegate with effective dates and permitted scope. It does not bypass conflict checks or let a requester’s name serve as their own approval. Material changes to a reviewed document invalidate the earlier decision for changed scope.
The Sales Rep’s eligible within-limit quote approval is an explicit exception to independent approval. PO approval remains independent even within a Buyer’s limit. Payment release requires an eligible Controller who did not prepare the run or approve its bills, and payroll approval excludes its preparer.
Protect sensitive changes and cutover evidence
Employee pay, identity and bank fields use explicit masking that overrides broad table access. HR Manager or Payroll Administrator proposes sensitive employee changes; a different person in the other role reviews them. Effective compensation and approval history remain available for later pay corrections.
Master changes retain old and new values, effective timing and approval evidence. Opening migration uses reviewed source identities, cutoff and control totals, with currencies and accounts available before dependent records and a second pass for cyclic references.
Opening stock, open items, asset books, payroll YTD and leave balances are reconciled as nonposting baselines alongside the authorized opening ledger. Loading history must not create new receipts, orders, invoices or bank instructions.
What it keeps track of
Data model- Entities
- Legal entities under a reporting parent. Each entity owns its trial balance, functional currency, fiscal calendar, tax registration and consolidation method.
- Currencies
- ISO currency codes used as functional, reporting and transaction currencies.
- Exchange rates
- Dated currency multipliers by source and type; required rates are reviewed and frozen on a transaction, with missing-rate exceptions blocking its financial action.
- Accounting periods
- Fiscal periods per entity with the open and close state the close checklist drives.
- Bank accounts
- The company’s own bank accounts per entity: where customer cash lands, where payment runs and payroll are paid from, and what the statement feed reconciles to.
- Cost centers
- Departments, projects, business units and locations that expense, budget and payroll are charged to.
- Departments
- Organisational departments per entity: Finance, Sales, Procurement, Production, Warehousing, HR, IT.
- Tax jurisdictions
- Authorities that levy tax and receive filings: country, state, province, city.
- Tax codes
- Named tax rates for a jurisdiction and direction, with the account they post to.
- Payment terms
- One list of terms shared by customers, vendors, invoices and bills, so the due date and the early-payment discount are computed the same way on both sides.
- Accounts
- Customer and vendor companies. A counterparty on both sides is one record with Type Both, with terms kept separately for each direction. A group entity that trades with this one is marked intercompany.
- Contact persons
- The people at an account: the buyer, the decision maker, the accounts-payable clerk, the engineer. Calls are logged against a person, quotes are addressed to one, and a lead converts into one.
- Approvals
- One row per approval step on any document: who was asked, who acted (and for whom, when delegated), what they decided and why.
- Enterprise policies
- Versioned entity authority, costing, matching and operating rules; inactive or unreviewed policy cannot authorise an action.
- Document revisions
- Immutable submitted, accepted, approved or posted snapshot; lifecycle changes cannot alter its content or human authority.
- Authority delegations
- Approved limited delegation preserves the actual actor, grantor and role scope; absence alone grants no authority.
- Master changes
- Proposed old/new effective master values and independent activation; protected fields never change by generic Manage permission.
- Product posting profiles
- Entity-specific effective cost and posting mapping for products and nonstock source classes.
- Integration events
- Authenticated inbound event or evidenced manual source; duplicate/late events cannot repeat financial or stock effects.
- Integration deliveries
- Durable outbound intent per destination and immutable source revision; transport success never proves the downstream business action.
- Migration batches
- Approved cutover manifest and nonposting import policy preserve history and suppress operational replays.
- Migration items
- Replay-safe source-to-target mapping and retained partial balances for each imported record.
Who uses it
Permissions- Admin
- Maintains identities, roles and governed configuration.
- Controller
- Owns financial reference data and period authority.
- Sales Manager
- And Buyer maintain their commercial counterparties.
- HR Manager
- Owns organizational data. and Payroll Administrator share the controlled employee-change path.
Set up Apparel & Footwear ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.