Post a social secretariat payroll export as a summary journal entry per pay run, not as one line per employee. Map each export column to a fixed ledger account, confirm that debits equal credits, and check the net pay total against your bank payment file before importing.
Key takeaways
- Post each payroll export as a summary journal entry per pay run, with one ledger line per account rather than one per employee.
- Map every export column to a fixed ledger account before the first import, and review that mapping whenever the provider changes its file format.
- Confirm that total debits equal total credits and that the net pay total matches the bank payment file for the same run.
- Keep the original export file linked to the journal entry so that every figure can be traced during an audit.
What does a social secretariat export contain?
The export is a summary of one pay run, produced from the payroll calculations your social secretariat performs. It normally groups amounts by type: gross remuneration, employer contributions, employee deductions and net pay due to staff. It is a calculation output, not a set of finished accounting entries, so it needs to be translated before it can be posted.
The exact column names and layout differ by provider. Treat the file layout as something to document once and verify on every run, rather than something you assume will stay the same.
Summary files and employee-level files
Some providers deliver a summary file with totals per category, while others deliver a detailed file with one row per employee and a summary sheet on top. Both can feed the ledger, but only the summary totals are needed for a standard journal entry. The employee rows are useful for reconciliation and for cost allocation.
How do you map export columns to ledger accounts?
You map each category of amount to one ledger account and keep that mapping in a documented table. Every column in the export should resolve to exactly one debit or credit account, with no column left to manual judgement during posting.
If the mapping has to run automatically on a regular schedule, the technical work sits in the connection between the payroll file and the ERP. Our system integration services cover that kind of file-based and API-based connection.
Gross pay and employer costs
Gross remuneration is an expense on payroll cost accounts, usually split by cost centre when your chart of accounts supports it. Employer social contributions form a separate expense group, so reports can show what the employee earns separately from what the employer adds on top.
Deductions and the net payable
Employee deductions are liabilities until they are paid to the tax authority or the social security office. Net pay creates a payable to employees that clears when the bank transfer leaves. Keeping these as separate accounts lets you reconcile each liability on its own schedule.
Should you post a summary or one line per employee?
Post a summary entry per pay run in most cases. Employee-level posting gives more detail, but it multiplies the lines you have to reconcile and makes the ledger harder to review.
The trade-off depends on what you need to allocate. A summary keeps the journal short and easy to check. Employee lines allow people costs to be assigned to projects or departments, which a single summary entry cannot do without a separate analytical file. Use employee detail only where that allocation is genuinely needed.
Which checks should run before the import?
Run five checks before the import. If any one of them fails, the import should stop until the cause is found, because a posted entry is much harder to correct than a held file.
- Confirm that total debits equal total credits.
- Compare the net pay total with the bank payment file for the same run.
- Check that the number of employees in the export matches the active staff list for that period.
- Verify that the run reference has not already been imported.
- Check that the period date is the period the pay run covers, not the date on which you happen to import it.
Teams that automate this step often add a rule that holds any file with an unmapped column. Held files are a normal outcome, and they are far cheaper to resolve than a wrong journal that has already been posted.
Where does this approach fail?
The approach fails when the export format changes without notice, when corrections arrive after posting, and when the chart of accounts drifts away from the mapping table. Each of these failures can look correct at first glance, which is why the checks above matter.
Corrections need particular care. Post a reversing entry against the original journal rather than editing it, and treat the corrected export as a new run with its own reference.
| Approach | Works well when | Breaks down when |
|---|---|---|
| Summary entry per pay run | Reconciliation is by pay run and the ledger should stay readable | Staff costs must be allocated to projects without a separate analytical file |
| One line per employee | People costs are allocated by project or department | Volume makes review slow and reconciliation error-prone |
| Manual re-keying of totals | The volume is very low and the file is rare | Staff turnover or pay run frequency increases, because keying errors accumulate |
Hypothetical examples of payroll postings
Here are two hypothetical scenarios:
In the first scenario, a company runs payroll once a month and imports a summary export. The net pay total in the draft journal does not match the bank file, because a final payment for a leaver was added to the bank file but not to the export. The pre-import check catches the difference, the import is held, and the team waits for a corrected export before posting.
In the second scenario, a company changes its social secretariat provider. The new file labels the employer contribution column differently from the old one. The mapping table is reviewed at the first run, shows that the label is unmapped, and the import is held until the mapping is updated and tested against the previous run.
Conclusion
Posting payroll exports into an ERP works best when the mapping is documented, the entry is kept at summary level, and the checks run before anything is posted. The same discipline makes the process easier to audit and easier to hand over. If you want to discuss how this connection could be built and maintained, you can request a project consultation or email info@ruicodex.com.
Frequently Asked Questions
Should I import a social secretariat export as one journal entry?
Usually yes, because one summary entry per pay run is the simplest approach that still reconciles cleanly. Keep employee detail out of the ledger unless you need project or department allocation, and store the original export file as the reference for the entry.
What should happen when the export format changes?
The import should stop until someone has reviewed the mapping. An unmapped column is a warning sign, not something to ignore. Update the mapping table, test it against a copy of the last run, and record the change so the history stays traceable.
How do I correct a payroll entry that has already been posted?
Post a reversing entry against the original journal, then post the corrected run under a new reference. Editing a posted entry removes the trail that auditors need to follow the change from the export to the ledger.
Who is responsible for the payroll calculations?
The social secretariat or payroll provider calculates the amounts, and your finance team is responsible for posting them correctly. Rui Codex provides technical implementation support for the connection between the files and the ERP, not payroll, accounting or audit advice.