Dates in Fr8labs

How Dates Are Managed in fr8Labs

A Compendium for Freight Forwarders Using the fr8Labs Accounting & Job Modules

1. Core Date Definitions

Accounting-Side Dates

  • Invoice Date The official date on the supplier’s or customer’s invoice. Treated as the legal document date.

  • Posting Date The date when the invoice is recorded in the general ledger. This can differ from the invoice date (e.g., backdating or aligning to operational milestones).

    • Posting Time is also captured for audit control (e.g., Malaysia requires posting within 72 hours).

  • Invoice Received Date The date when the invoice is physically received by your organization (e.g., when stamped at arrival).

    • Still required in some markets such as Indonesia and the Philippines, where payment terms are measured from receipt rather than invoice issue date.

    • In markets like Singapore, this field is often hidden as it is redundant.

  • Due Date Computed automatically from the partner’s credit terms. Users with permission can override this field per invoice.

Operations-Side Dates

  • Job Date The date the shipment/job record is created.

  • Job Month The reporting month for a job. Configurable to be based either on the job’s creation date or on ETD (export) / ETA (import).

  • Ops Completed / Job Closure Date Marks the point when operations are complete and financials should be reconciled. Often used for month-end cut-off.

  • ETD / ETA

    • Estimated Time of Departure (mandatory for exports).

    • Estimated Time of Arrival (mandatory for imports). These are operational anchor dates for performance tracking and reporting.

2. System Settings in fr8Labs (what’s configurable in fr8Labs)

  1. Job Month

    • Option A: Based on job creation date.

    • Option B: Based on ETD (exports) or ETA (imports).

  2. Invoice Date

    • Option A: Based on ETD/ETA.

    • Option B (most common): Based on invoice creation date.

  3. Posting Date

    • Option A: Based on ETD/ETA.

    • Option B: Based on invoice creation date.

    • Coupling Toggle: You can configure whether the posting date auto-aligns with invoice date changes, or remains independent.

  4. Due Date

    • Defaults from partner master data.

    • Editable per invoice by authorized users.

    • Roadmap: Split credit terms by direction (import vs export) and by invoice type (e.g., disbursements = COD, regular sales = standard terms).

3. Why Dates Matter

  • Financial Reporting Dates drive compliance with accrual accounting and revenue recognition standards. Correct alignment ensures revenues and costs fall into the right periods.

  • Operational Performance Forwarders often view profitability at the job level (linked to ETD/ETA), which doesn’t always match financial accounting P&L timing.

  • Controls Posting date and time provide guardrails against backdating, help ensure auditability, and support local compliance requirements.

4. Tricky Scenarios for Forwarders

Scenario A: Door-to-door shipments

  • Suppliers are paid early.

  • Customer invoices may only be raised 2–3 months later (at final delivery).

  • Problem: Costs hit months before revenues, leading to distorted margins unless accruals or milestone-based recognition are used.

Scenario B: Regular shipments

  • Shipping line requires prepayment.

  • Customers are invoiced on ETD/ETA.

  • Supplier invoices from agents, truckers, or warehouses may arrive 1–2 months later.

  • Problem: Revenue is recognized upfront, but supplier costs lag, causing P&L timing gaps.

5. Methods for Handling Dates

Method 1A: Strict Accruals (Per Job)

  • What: At month-end, create accrual entries for every cost or revenue that belongs to the job but hasn’t yet been invoiced. Reverse them when the actual invoice arrives.

  • Pros:

    • Gives you the most accurate profit per month.

    • Ensures revenues and costs are always matched to the right period.

  • Cons:

    • Heavy workload — requires ops to close jobs on time and finance to process many accrual entries.

    • Easy to fall behind if teams aren’t disciplined.

Method 1B: Flexible / Materiality-Based Accruals

  • What: Instead of accruing every missing invoice, you have two common approaches:

    • Threshold-based: Only accrue the big or important items (e.g., anything above $X).

    • Report-based: Use the fr8Labs Job Management Report at month-end to find all jobs with estimated sales/costs that haven’t been invoiced, and accrue them in one lump sum entry.

  • Pros:

    • Much easier to do compared to strict accruals.

    • Captures the majority of financial impact without creating dozens of small accrual entries.

    • If using the report-based method, thresholds don’t matter — you sweep everything in one pass.

  • Cons:

    • Monthly profit may still be a little off if accruals are approximate or lumped.

    • Accuracy depends on ops discipline in keeping job estimates up to date.

Method 2: WIP / Contract-Asset Method

  • What: Book all invoices into “Work-in-Progress” accounts on the balance sheet first. Only move them into revenue/cost once the job is officially closed. (Not natively available in fr8labs today as not our recommendation).

  • Pros:

    • Job closure directly controls when revenue and cost hit the P&L, which feels natural for ops teams.

    • Keeps job-level reporting in sync with financials.

  • Cons:

    • Risky if jobs aren’t closed on time — revenue and costs can sit in WIP too long.

    • Needs strict rules and controls to avoid misuse.

    • Not the cleanest method under accounting standards unless properly treated as contract assets/liabilities.

Method 3: Posting Date Alignment to ETD/ETA/Job Date

  • What: Keep invoice date as the document date, but make the posting date automatically match the ETD, ETA, or Job Date.

  • Pros:

    • Simple and intuitive — ops dates line up with accounting dates.

    • Makes job-level reporting look more realistic.

  • Cons:

    • Month-end accounts can’t be fully “closed” until all late invoices are received or accrued.

    • Can still cause timing gaps if supplier invoices are slow to arrive.

  • NOTE: if this method is chosen, please notify your fr8labs representative to also switch on “ETD/ ETA posting date sync changes”. This is to cater for the scenario where vessel delay, and the ETD/ETA crosses a month, all existing invoice posting dates needs to be synced to the latest ETD/ETA

Method 4: Invoice & Posting Dates = Creation/Invoice Date (Accept Divergence)

  • What: Leave both invoice date and posting date as the creation date (document date). Don’t try to realign them.

  • Pros:

    • Easiest and cleanest process — no need to re-date invoices.

    • Lowest admin effort for ops and finance.

  • Cons:

    • Job P&L (ops view) and Accounting P&L (finance view) will not match exactly.

    • Teams must be trained to understand and accept the difference.

6. Recommendations by Company Size

  • Lean Teams (1–20 users)

    • Default to Method 4: invoice + posting date = creation/invoice date.

    • Use Job P&L dashboards for operational visibility.

    • Educate staff that Job P&L ≠ Accounting P&L.

    • Optional: material accruals for large variances.

  • Growing Teams (20–100 users)

    • Job Month = ETD/ETA.

    • Invoice Date = creation date.

    • Posting Date = ETD/ETA (Method 3).

    • Add material accruals (Method 1B) at month-end.

    • Provide dual reporting: Job P&L vs Financial P&L.

  • Networked Teams (>100 users)

    • Formal accrual policies (Method 1A) and/or WIP method (Method 2).

    • IFRS-compliant revenue recognition policies (over-time vs point-in-time).

    • Strict job closure SLAs

    • Reconciliation dashboards across job, accrual, and statutory P&L.

7. Implementation Checklist

  1. Configure Job Month basis (creation vs ETD/ETA).

  2. Set Invoice Date default (creation vs ETD/ETA).

  3. Decide Posting Date default and whether it auto-aligns with invoice date.

  4. Lock Due Date to partner terms and define override permissions.

  5. Choose accrual policy (none, material, strict).

  6. Define Job Closure rules and enforce SLAs.

  7. Educate teams on Job P&L vs Financial P&L differences.

  8. Document anti-backdating and compliance practices (e.g., Malaysia’s 72-hour posting rule due to e-invoice requirements).

8. Glossary

  • Invoice Date – Supplier/customer invoice date (legal).

  • Posting Date – Date the entry is recognized in the ledger.

  • Due Date – Based on partner credit terms.

  • Job Date – When shipment/job record is created.

  • Job Month – Reporting month of the job (creation vs ETD/ETA).

  • Ops Completed / Job Closure Date – Milestone for closing operations and financial cut-off.

  • ETD (Estimated Time of Departure) – Mandatory for exports.

  • ETA (Estimated Time of Arrival) – Mandatory for imports.

Documentation owner: Fr8Labs Customer Success. Formatting reviewed: 21 September 2026; product behaviour not reverified in this formatting pass.