Skip to main content
GullySystem
Professional services

Invoice Management for Architecture firms

Create and track invoices against billed goods or work.

Finance & Accounting

Does this function belong in your operation?

Use when bills need links to orders, delivery or completed work.

A supply or milestone becomes billable.

Architectural billing should start from the signed fee arrangement and the evidence required for each design stage. Configure concept, detailed-design or site-stage charges according to that agreement rather than treating a drawing upload as automatic permission to invoice. Additional design work and reimbursable expenses need their own approved basis so the client can understand the amount billed. Keep consultant costs and the practice's own fee distinct unless the appointment explicitly combines them. A consultant invoice arriving at the studio does not itself create a client charge. Accounts needs the agreed recovery arrangement and project approval before including that cost, with the source document retained for the client's query.

Bring the records the workflow depends on.

  • Executed appointment and stage-fee schedule
  • Recorded milestone acceptance or agreed billing trigger
  • Approved variations and reimbursable expenses
  • Client billing contact, advances and prior invoices

Outputs to check

  • Stage-fee invoice and supporting reference
  • Unbilled approved work by project
  • Client balance with allocated receipts and credits

Follow the invoice management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Identify billable work

    Use the approved order, delivery or milestone reference.

  2. 2. Prepare invoice lines

    Check customer details, quantities, rates and tax settings.

  3. 3. Approve and issue

    Assign the authorised number and retain the issued document.

  4. 4. Send required handoffs

    Pass applicable documents to accounting or electronic registration processes.

  5. 5. Track settlement

    Allocate receipts and handle disputes or credits without overwriting the issued invoice.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Project architect

Supplies the evidence that the contractual stage or agreed billing event has been reached.

Accounts preparer

Checks the fee schedule, earlier bills and approved extras before issuing the next invoice.

Principal or authorised commercial owner

Resolves disputed scope and approves changes to the fee basis.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Client comments keep a stage open

Review the contract's billing condition rather than billing from an internal completed status alone.

Additional design requested

Link the approved fee variation before adding a new charge.

Advance paid by another party

Record the payer and allocation without changing the named contracting client silently.

Can this work independently?

Invoicing can work from entered approved lines without order or stock modules. Connections bring in accepted quantities and pass receivables to accounting. e-Invoicing, payment collection and stock dispatch are distinct processes; issuing a bill does not confirm any of them occurred.

Systems and records it connects with

  • Receipts management: Recorded customer payments and invoice allocations.
  • E-invoicing: Applicable invoice-registration references and response status.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Accounting software: Posted financial entries and reconciliation references.

Configure, test and introduce the workflow.

  • Send sample invoices and your numbering. Staff see a list of tax details and the layout to match.
  • Confirm the face of the bill. A test invoice from a test order comes back for inspection. Share unpaid bills and customer balances. They load as a trial and show on the overdue list for accounts to check.
  • Sales and accounts staff practise on test orders. Short sheets for each role follow. The new series begins on the date you fix. The first overdue list is reviewed together.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Every stage invoice identifies its fee basis and supporting event.
  • Previously billed stages cannot be charged again without an authorised adjustment.
  • The project balance reconciles advances, stage bills, receipts and approved credits.
Architecture firms

How the business operates.

Architecture Firm Management Software is a practice system that GullySystem sets up for architects, from single-architect studios to firms with project architects, draughtsmen and site supervision. It holds plot details, numbered drawing revisions, authority submissions, consultant lists and site visit reports, and each bill matches the fee agreed for its stage. Nothing is retyped between them.

Projects and site records

Hold the plot, site address, survey number, plot and built-up area, building type and the appointment terms for each project, so nothing about the brief is searched for. Site facts sit together.

Design stages and milestones

Move a project through concept, schematic, detailed design, good-for-construction and site stage, with the date each stage was reached and who moved it. Stages are visible across jobs.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Projects and site records. Hold the plot, site address, survey number, plot and built-up area, building type and the appointment terms for each project, so nothing about the brief is searched for. Site facts sit together.
  • Design stages and milestones. Move a project through concept, schematic, detailed design, good-for-construction and site stage, with the date each stage was reached and who moved it. Stages are visible across jobs.
  • Drawing register and revisions. Number every plan, section, elevation and detail, and keep each revision with its reason, author and date in one register, so the current sheet is never in doubt. Superseded sheets are marked.
  • Drawing issue and transmittals. Record which set went to the client, consultant or contractor, as a print, a PDF or a message attachment, and whether anyone acknowledged receipt. Holders of old prints show up.

Operational bottlenecks to check

Drawing revisions lose their trail

A plan goes out as one revision, then another, and the site builds from an older print, while the date and recipient of each issue sit in mail threads. Nobody can prove who held which print.

Design stages are not visible together

Concept, schematic, detailed design and good-for-construction run at once across several projects, so nobody can say in a single place which job is sitting at which stage. The diary tells half of it.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and brief

    An owner or builder arrives with a plot and a requirement, and the site address, plot area, rooms wanted and appointment terms are recorded against a new project. The brief stays with the file.

  2. 2. Concept and schematic design

    The studio prepares site analysis, concept options and schematic plans, each drawing takes a number in the register, and the client’s comments are logged against the option shown. Every choice stays traceable.

  3. 3. Approval submission

    Submission drawings are prepared for the local authority and lodged with the forms your office uses, and each submission, query and reply is dated and kept with the project. Anyone can pick up the file.

  4. 4. Detailed drawings and tender

    Good-for-construction sets, services drawings, door and window schedules and a quantity list are built up, consultant inputs are logged as they arrive, and tender sets go out to contractors. Each tender set is numbered.

  5. 5. Construction stage

    Site visits are logged with photographs, deviations and instructions for the contractor, and revisions raised on site are numbered and reissued to everyone holding the older print. Old prints are withdrawn.

  6. 6. Stage billing and handover

    A completed stage is marked and a bill goes out for the amount set in the appointment, while as-built drawings and the final set are handed over and recorded. The file then closes.

Industry reports to connect with

  • Projects by design stage and project architect
  • Drawings issued and revisions pending by sheet number
  • Authority submissions and queries open
  • Site visits made and snags closed by contractor

Questions before implementation.

When should architecture firms consider invoice management?

Use when bills need links to orders, delivery or completed work. A supply or milestone becomes billable.

What should we bring to the requirements discussion?

Bring anonymised examples of Executed appointment and stage-fee schedule; Recorded milestone acceptance or agreed billing trigger; Approved variations and reimbursable expenses; Client billing contact, advances and prior invoices. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Create and track invoices against billed goods or work. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Your accountant confirms tax treatment and invoice requirements.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Every stage invoice identifies its fee basis and supporting event. Use this check when reviewing the first working version.

Talk to us

Discuss invoice management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements