Back to blog
TipsOctober 23, 20264 min read

The one payment-terms field to fix before billing a corporate client across a fiscal-year boundary

Sending a NET 60 invoice in late November to a corporate client can push payment into their next fiscal year — and freeze it there. Here's the one field to change first.

By ZenPay Team

Share
The one payment-terms field to fix before billing a corporate client across a fiscal-year boundary
Photo by Dallas Penner on Unsplash

Your corporate client's fiscal year ends December 31. You send them a $22,000 invoice on November 28 with your standard NET 60 terms. Payment is technically due January 27 — inside the next fiscal year. Their accounts payable team flags it as a new-year liability, routes it through a fresh approval cycle, and you wait another six weeks. A single field caused all of it.

Why fiscal-year boundaries are a billing trap for law firms

Corporate clients run their AP queues against budget cycles, not calendar months. An invoice that lands inside one fiscal year but falls due in the next gets reclassified. It stops being a Q4 payable and becomes a Q1 encumbrance. That triggers a second approval chain, sometimes a new purchase order, and almost always a longer wait.

For a solo or small-partner firm billing hourly and retainer work, this is particularly painful. You've already done the work. The hours are logged. The disbursements are accounted for. But because the due date crossed a line on the corporate calendar, your $22,000 sits in limbo through January and into February.

The field causing the problem is payment terms. Specifically, the due-date calculation that flows from them.

The one field: payment terms, and what to change it to

NET 60 is your default because large corporate clients demanded it when you onboarded them. That's fair. But NET 60 is not a law; it's a preset. And on invoices issued within 60 days of a client's fiscal year-end, it reliably misfires.

The fix is to switch that single invoice to "Due on receipt" or a shorter preset like Net 14 or Net 30, and to communicate the reason proactively. Something like: "Given the year-end timing, we've set this invoice to Net 30 to keep it within your current fiscal year's AP cycle. Please let us know if you need anything adjusted."

Most corporate clients will accept this. Their own finance teams often prefer it: a payable cleared before December 31 is cleaner than one that rolls into Q1 with an open PO.

When to make the call

Work backwards from your client's fiscal year-end. If the due date under your standard terms would fall after that date, change the terms before you send. The threshold varies:

  • NET 60 invoice: flag anything sent after November 1 (60 days before December 31)
  • NET 30 invoice: flag anything sent after December 1
  • NET 14 invoice: flag anything sent after December 17

Build this check into your end-of-year billing run. It takes thirty seconds per invoice and saves weeks of follow-up.

What to do with retainer invoices specifically

Retainer invoices are cleaner because they're predictable. If you auto-send a monthly retainer on the 1st of each month, your December 1 invoice on NET 30 terms lands exactly on December 31. Fine. But if your retainer runs on NET 60, the December invoice is already a January liability by definition. Either negotiate a one-time terms override for December, or bill the December retainer early (November 25, say) so that even NET 30 clears before year-end.

How most firms handle year-end invoicing

  • Default NET 60 terms apply to every invoice regardless of send date.
  • Manually checking fiscal-year conflicts across 8–12 active corporate matters is easy to miss.
  • Changing terms means editing a Word or PDF template and re-sending manually.
  • A missed terms change means a delayed payment, a second approval chain, and awkward follow-up calls.

How ZenPay handles it

  • Payment terms presets (Net 14, Net 30, Net 60, Due on receipt, custom days) are set per invoice in two taps, with no template editing.
  • Auto-reminders fire N days before and after the due date in your name, so the client's AP team gets a nudge even during the holiday slowdown.
  • Recurring invoices for monthly retainers let you set a one-off terms override on a single billing cycle without touching the recurring schedule.
  • Per-invoice payment tracking shows partial payments, write-offs, and due dates across all matters in one view, so nothing slips into January unnoticed.

How to frame the conversation with the client

Proactive communication is the difference between a client who accommodates the change and one who escalates it to procurement. A short note in the invoice email is enough:

"We've set this invoice to Net 30 rather than our usual Net 60 given your December 31 year-end. This keeps the payable within your current fiscal year and simplifies your AP close. Happy to discuss if your team needs a different arrangement."

That framing does two things. It signals that you understand how their finance team works (which most outside counsel doesn't bother with), and it gives their AP contact a ready-made explanation for their manager. You're making their job easier, not demanding a favour.

Build this into your Q4 billing checklist

Year-end billing is already compressed. Partners are finalising WIP, trust account reconciliations need sign-off, and everyone is watching the AR ageing report. Adding a fiscal-year-boundary check to that list sounds like one more thing. It isn't. It's a one-column filter on your outstanding invoices: "Does this due date fall after December 31?"

Invoices that clear inside the client's fiscal year get paid faster, with fewer approval loops, and with less damage to the relationship than a chaser call in mid-January. The terms field is the only thing standing between you and that outcome.

Less admin.
More of what matters.

Your first invoice
within 2 minutes.

1Sign up — free
2Add your first client
3Send your invoice

Free forever.
No catch.

€0

To get started

No credit card. No trial. Just free.

Start free

Keep reading