Skip to content
ERP implementation

ERP implementation: the accounting module as the core of the system

Cristina Rolón's specialty: getting the accounting module configured properly so that everything else in the ERP — treasury, logistics, production, purchasing, banking — reconciles, and stays traceable and auditable.

The starting point

Why the accounting module is the parent of every other module

In an ERP, everything eventually lands in the accounting records. A sale generates a journal entry; a purchase creates a liability and an IVA (value added tax) input credit; a warehouse movement changes inventory valuation; a work order consumes raw materials and generates cost; a collection moves treasury and the bank accounts. If the accounting module is configured badly, all of those movements are recorded incorrectly — or not recorded at all — and the rest of the system starts producing information that does not add up.

That is why an ERP implementation is not won on the attractive screens of each module: it is won in the chart of accounts, in the automatic posting rules, in inventory valuation, in the cost centers and in how the subledgers integrate with the general ledger. When that groundwork is done properly, the company gets reliable financial statements without a parallel manual effort; when it is done badly, the team ends up rebuilding everything in spreadsheets.

Cristina Rolón works at exactly that point: she joins the ERP project from the accounting and tax perspective, defines how each business transaction has to be recorded in Paraguay — including the requirements of DNIT (Paraguay's tax authority) and electronic invoicing — and stays with the project until the closings come out of the system rather than out of a spreadsheet.

Integration

The modules that depend on the accounting core

Each of these modules either generates or consumes accounting information. The implementation defines how it is recorded, how it is reconciled and how it is audited.

Treasury and cash

Collections, payments, petty cash funds and cash counts, with automatic posting and reconciliation against the accounting balances.

Banking and reconciliation

Statements, checks, transfers and periodic bank reconciliation, with outstanding items clearly identified.

Purchasing and accounts payable

Purchase orders, goods receipt, supplier invoice and payment, with three-way match control and IVA input credit correctly claimed.

Sales and accounts receivable

Electronic invoicing, credit notes, collections and aging of balances, integrated into the sales ledger.

Inventory and logistics

Receipts, issues, transfers between warehouses and inventory valuation, with a direct impact on cost of goods sold.

Production

Work orders, raw material consumption, labor and manufacturing overhead applied to the cost of finished goods.

Dispatch and delivery notes

Delivery notes and shipments linked to the invoice and to the stock movement, so nothing leaves without supporting documentation.

Fixed assets

Additions, disposals, depreciation and revaluations, with their impact on results and on the financial statements.

Costing and profitability

Cost centers, costing by product, line or project, and the real margin of each business unit.

The outcome

What a company should be able to do once the ERP is properly implemented

  • Produce the income statement and balance sheet straight out of the system, without assembling them by hand in spreadsheets.
  • See real profitability by product, business line, branch or project, with costs properly applied.
  • Trace any number backwards: from the income statement to the journal entry, and from the entry to the source document.
  • Reconcile banks, inventory and customer accounts without arguments over which system is right.
  • Close the month on time, with the subledgers tied out against the general ledger.
  • Respond to a DNIT tax audit by showing the full audit trail from within the system.
  • Control access and keep a record of who entered, modified or approved each transaction.

Traceability and auditability are not a luxury: they are what allows management to trust the numbers, and what allows an external auditor, a bank or the tax authority to verify what the company reports.

Experience

More than 30 companies implemented, from 10 to over 700 employees

Cristina Rolón has taken part in the implementation of the ERP accounting module at more than 30 companies of different sizes and industries: from small companies of around 10 employees to organizations with more than 700 employees, several branches, in-house production and complex cost structures.

That difference in scale matters. A ten-person company needs a simple system, a manageable chart of accounts and processes that do not suffocate it; a company of seven hundred needs cost centers, access profiles by area, approval controls and closings coordinated across several teams. The implementation has to fit the real size of the operation, not the software brochure.

That track record also produced a clear reading of where these projects usually fail: charts of accounts copied from another company, opening balances migrated without being reconciled, modules switched on before the accounting counterpart of each transaction has been defined, and training that teaches people which buttons to press but not what each button actually records.

Methodology

How we run an implementation

1

Business review

We map the real cycle: what happens from the moment an order comes in until it is collected and recorded.

2

Chart of accounts design

Building or redesigning the chart of accounts and the cost centers around the way management needs to read the information.

3

Accounting configuration

Automatic posting rules, subledgers, treatment of IVA and withholdings, inventory valuation and costing criteria.

4

Balance migration and reconciliation

Loading reconciled opening balances, so the system starts out tied and does not carry differences forward.

5

End-to-end testing

Simulating real transactions from start to finish, verifying the accounting impact of each module before going live.

6

Team training

Role-based training, so that every area understands what the system records when it operates and what the consequences are.

7

Go-live and support

Launch, an assisted first month-end close and fine-tuning until the financial statements come out of the ERP without rework.

Frequently asked questions

About ERP implementation in Paraguay

MCG's work is the accounting content of the implementation, not the sale of a license: chart of accounts, posting rules, valuation and costing criteria, treatment of IVA and withholdings, reconciliations and closings. That content is applied to whichever ERP the company has chosen or is evaluating, and it is coordinated with the software vendor and with the company's IT team.
Because every other module ultimately posts into it. If logistics, production or treasury are switched on before it has been defined how each movement is posted, the system starts generating incomplete or misclassified records, and correcting them later means reprocessing months of information. Defining the accounting core first is what saves exactly that rework.
Yes, and it is an important part of what we do. It starts with a diagnostic: reviewing the chart of accounts, checking whether the subledgers tie out to the general ledger, reviewing inventory valuation and the migrated balances, and identifying which transactions are being recorded incorrectly. From there we build a remediation plan by priority, without bringing the operation to a halt.
Every figure has to be traceable back to its source document, access has to be defined by role, there has to be a record of who entered and approved each transaction, the subledgers have to tie out to the general ledger, and the supporting documentation has to be available. That is what makes it possible to respond confidently to an external auditor, a bank or a DNIT tax audit.
It is useful for both, with different scopes. A ten-person company needs a simple chart of accounts and light processes that still leave a traceable record; a company with hundreds of employees needs cost centers, access profiles, approval controls and coordinated closings. We have worked at both ends, and the most common mistake is applying the model of one to the other.

About to implement — or fix — an ERP?

Tell us what stage the project is at and we will review it together.

Talk to us