Begin with six questions
A useful contractor operation should answer these questions without a search through email:
- Who is working with the company?
- What agreement and rate apply now?
- What work and expenses were submitted?
- What has been reviewed, and what still needs action?
- What does the company owe?
- What has been paid, and what is still owed?
Give each record one job
Confusion usually begins when one document is asked to prove too much. An agreement records the terms in use. A Time Entry records when work happened. A Timesheet groups work for review. An invoice states what the contractor is billing. An amount review confirms what the company owes. A payment record shows what was paid and what remains.
Those records should support one another without becoming interchangeable. An approved Timesheet is not proof that money moved. A finalized invoice is not a payment. A bank transfer does not explain which work it covered unless the business connects it to the right amount.
This distinction is not bureaucracy for its own sake. It lets each person understand what a record means and what should happen next.
- Agreement
- What terms apply?
The terms in use for the working arrangement.
- Time Entry
- When did the work happen?
The individual record of time worked.
- Timesheet
- What work is ready for review?
Time Entries grouped for a review decision.
- Invoice
- What is the contractor billing?
The amount and work the contractor presents for payment.
- Amount review
- What does the company owe?
The recognized amount connected to its supporting records.
- Payment record
- What was paid, and what remains?
Evidence of an external payment and the remaining balance.
Use the records that apply to the work. This map is not a required sequence. Approval and review do not move money.
Use states that point forward
A small set of precise states is more useful than a maze of custom colors and internal codes. Draft means the person is still working. Submitted means a review is waiting. Changes requested tells the contractor to correct and resubmit. Approved means a reviewer accepted the item. Ready to pay means the final amount is confirmed, but no payment has necessarily moved. Partially paid means a balance remains.
The wording matters. “Processed” is misleading if all that happened was a successful database update. “Paid” is wrong if someone merely approved an amount. Clear states prevent expensive assumptions.
Separate visibility from authority
The person who needs to see whether a contractor is working may not need to see the contractor’s rate. A Team Lead may need to review time without receiving invoice or payment access.
Start with the people they lead. Then decide whether they can see current work, review time, approve Timesheets, or view financial records. Financial access should be an explicit choice, not a side effect of assigning someone a team.
Create one place for unfinished work
Spreadsheets are good at listing data. They are less useful at answering, “What needs me now?”
A practical attention list names the issue and the next action: a Timesheet awaiting review, an invoice mismatch, a missing rate, or a payment the company has not entered. Once the issue is resolved, it leaves the active list. That is more useful than a dashboard full of totals that still asks the user to investigate every row.
Keep a spreadsheet when it still makes the decision clear
Excel or Google Sheets can be a sensible choice for a small, stable operation with one responsible reviewer. A spreadsheet is not automatically a broken process. Keep it if everyone can identify the current source, approval and payment history without rebuilding the answer each month.
Use separate record IDs for work, invoices and payments. Keep the person, period, rate, approved hours, approved expenses and payment reference explicit. A supporting invoice for the same work is not another cost. For fictional approved work of USD 500 plus a USD 25 expense, a matching USD 525 invoice supports the same obligation. After USD 200 is paid elsewhere, USD 325 remains.
Use Excel data validation to constrain routine inputs. In Google Sheets, protected ranges can restrict editing, but they do not make shared compensation data confidential: people with access may still see or copy it. Decide file access separately from formula protection.
Try the downloadable review worksheet for a structured manual check, or use the no-account balance worksheet for the arithmetic. Neither imports into Friday Falcon or substitutes for approval. Keep the supporting records in your existing system.
Consider a shared application when recurring corrections, multiple reviewers or different financial permissions make that manual process hard to maintain. The software comparison library separates time capture, agency planning, accounting and contractor review so you can fix the actual gap.
Move in stages
Do not rebuild the whole operation in one weekend. Move the records in the order that gives each later step something reliable to use:
- Add contractors and current access.
- Record the agreement and rate in use.
- Move time and Timesheet review into one repeatable flow.
- Connect invoices and confirmed amounts.
- Add payment evidence and remaining balances.