How it works

How an engagement runs in LedgersLines.

From the first document group to the closed file, in nine steps. Your team needs no training. Your clients never see more than their own part.

  1. Once per firm

    Set your firm’s standard once.

    Document groups are the request lists your firm sends again and again: statutory, payroll, banking, revenue. Four come seeded when you sign up. Add the documents each group needs, mark which are required, and note the file types you accept. Every audit that uses a group starts from this list, so a new joiner sends the same request list as your most senior manager.

    • Four starter groups, seeded on sign-up
    • Required or optional, per document
    • Accepted file types, per document
  2. Per client

    Answer the company details.

    Add the client, then answer a few facts about the company: its legal form, its size, whether it runs a payroll. The facts decide which audits apply and which document groups are in scope. Each answer is dated and keeps its history, so you can show why a group was in or out for a given period. The decision stays with the firm; the facts make it quick.

    • Every answer dated, with its history
    • Unanswered facts go to the client as questions
    • A scoping aid; the firm decides
  3. Per engagement

    Issue the request list in one step.

    Open the audit and the checklist is already drafted from the groups in scope, each request with a due date. Check it, move a date or add a one-off request, then press Send requests. Nothing reaches the client before that. Sending stamps the dates and opens the client’s portal.

    • A draft first; the client sees nothing until you send
    • Due dates per request, or across the whole audit
    • One-off requests added to any group
  4. Per client

    Each contact sees only their part.

    Create the client’s roles, such as HR Manager or Treasury Lead, and set which document groups each one reaches, down to single documents. Invite people by email, or hand out the client’s access code; anyone who joins with the code waits until you give them a role. Change a role and everyone who holds it sees the difference at once.

    • Reach set per group, and per document
    • Invite by email, or with the access code
    • Client contacts are free and unlimited
  5. The client

    Priya opens her portal.

    Priya, Northwind’s HR Manager, signs in and sees Documents requested: only the Payroll & HR requests, each with its due date, a short description and an Upload button. There is nothing to install and no spreadsheet to keep up to date. Questions from your team appear in the same place.

    • Only the groups her role covers
    • Due dates and required marks on every request
    • Questions from the auditor, in the same place
  6. Every upload

    Straight into the checklist.

    She uploads the file against its request. It lands as version 1 and moves to awaiting review in your queue. Nothing travels by email. The file type is checked against the file’s contents on upload, not just its name, and she can replace the file until it is approved.

    • Up to 50 MB a file, type checked on upload
    • Replace freely until it is approved
    • Every version kept
  7. Review

    Every upload lands in one review queue.

    The upload appears in the client’s review queue, oldest first. Open the file, then approve it, or request changes with a note. Approving settles the document and locks it for the client. Requesting changes asks for a new version, and the client only ever sees the words you write, next to the request.

    • Oldest first, across every audit for the client
    • Approve settles and locks the document
    • Request changes, with a note the client sees
  8. Review

    Version 2 lands. Version 1 stays.

    When Priya replaces the file, it arrives as version 2. Version 1 and your note stay on the record, so the file shows who sent what, when, and what you decided. Requests that pass their due date are flagged as overdue on their own, ready for a reminder.

    • Every version and decision kept for the file
    • Overdue flagged on its own
    • Reminders sent from the request
  9. Across the firm

    See every client’s position without asking.

    The Clients page shows every engagement at once: what is approved, what waits on your review, what waits on the client and what is overdue. Filter by stage or lead, or export the request list as a PBC file. When the last document is approved, mark the audit completed and the record is done.

    • Counts from the same records, never rolled up by hand
    • Filter by stage, audit type or lead
    • Export the request list (PBC) as CSV

LedgersLines

  1. 01

    Fieldwork starts with the documents in hand.

  2. 02

    A clean, audit-ready record.

  3. 03

    Clients see only their part.

From $49 a month · Client contacts free and unlimited · Cancel any time