Versioned cargo tariffs
Cargo rates are selected by cargo type, company and effective date, then copied to the worksheet so later tariff edits do not rewrite historical commercial decisions.
Case study
Fejudamportal.fejudam.com ↗
From financial calculations to a controlled operating record.
Cargo billing, Nigerian TAS payroll and finance reporting are connected through tariff rules, approvals, accounting entries, documents and employee self-service.
3finance and operations applications
7payroll lifecycle states
4relief-evidence states
5+document outputs
The operating problem
Finance-heavy operations need calculations people can trace, not just totals they can see.
The challenge
Cargo billing and payroll both combine rules, effective dates, exceptions, approvals and accounting consequences. The platform needed to turn those calculations into linked records that finance could review, post and explain later.
The design question
How do you preserve management approval and tariff judgement while removing the repeated reconstruction of invoices, payroll outputs, employee documents and reporting views?
The connected operating journey
One record moving through the business.
01InputCargo or payroll facts
→02RulesTariff or statutory logic
→03ReviewOperator and manager control
→04PostAccounting invoice or journal
→05DocumentPDFs, schedules and payslips
→06ReportPosted-entry visibility
What the system connects
Automation around the rules. Human control around the decisions.
Dual-currency cargo billing
A reviewed cargo worksheet can create linked USD and NGN accounting invoices while checking the generated totals against the operational calculation.
Controlled Nigerian TAS payroll
Gross pay, statutory deductions, approved reliefs, taxes and expected receipt move through calculation, exception review, manager approval and accounting posting.
Employee payroll self-service
Employees can retrieve approved payslips and submit relief evidence with supporting files while payroll managers retain approval authority.
Finance command centre
Finance views are built from posted journal entries with drill-through to source records rather than detached reporting copies.
Document and audit continuity
Invoices, cargo reports, bank schedules, payslips and accounting entries remain connected to the operational records that produced them.
What changed
The process became a connected operating flow, not a collection of screens.
Cargo billing and payroll both combine rules, effective dates, exceptions, approvals and accounting consequences. The platform needed to turn those calculations into linked records that finance could review, post and explain later.
Rates, calculations, approvals, accounting entries and employee-facing documents now form traceable workflows rather than isolated finance outputs.
The value is not removing judgement. It is making the judgement point explicit and keeping everything around it connected.
The Nadmaa approach
Business analysis first. Technology second.
Rates, shipping facts, payroll inputs, approvals and accounting outputs all needed to stay in the same record chain. Nadmaa preserved review where it matters and removed the rebuild around it.
Fix the process. Connect the systems. Build what's missing.
Where is your operation still being rebuilt by hand?
Bring us the operating problem.
You do not need to know the technology answer. We can map the workflow with you and identify what is worth fixing first.