Clock Clerk
Start free trial

Workflows

Pay contractors

A contractor records their hours like everyone else. At the end of each month they submit it on My Month, which turns the month's hours into two documents: an acceptance protocol for the organization to sign and an invoice for it to pay. Their engagement manager countersigns the protocol, Finance approves the month for payment and records the money going. While a month is submitted its hours are locked, and once it is approved for payment they are final.

Who does what

StepWhoWhere
Make someone a contractor, and choose or change their engagement managerAdministrators.Contractor profiles
Keep the rest of a contractor's profile, and confirm their payment detailsFinance and administrators.Contractor profiles
Set what a contractor is paidFinance and administrators.Team costs
Record hours, and submit or withdraw the monthThe contractor.My Week, My Month
Countersign the protocolThe contractor's engagement manager, any administrator, or someone in Finance with Can countersign contractor months. Never the contractor.Contractors
Send a month backThe engagement manager, Finance and administrators. Never the contractor.Contractors
Approve a month for payment, take the payment file and mark a month paidFinance and administrators.Contractors

Nobody countersigns their own month. A profile cannot name the contractor as their own engagement manager, and an administrator or someone in Finance who is also paid as a contractor cannot countersign or send back their own month; the app refuses with You cannot accept your own month. A Manager sees Contractors in the menu only once a profile names them, and then only the contractors whose profiles do. Roles says more about who a contractor is.

Before you start

1. Make someone a contractor

For administrators. A person is a contractor because they have a contractor profile, and for no other reason. They keep their role and their sign-in.

  1. Choose Contractors in the menu, under Payables, then Profiles at the top.
  2. Choose New contractor, and under Who is the contractor pick the person.
  3. Fill in their Legal entity: who the documents are from, which is the company if they contract through one (Legal name, Address, Tax id and what it is called, Registration no., Billing email).
  4. Under How they are paid, choose Bank transfer (Bank, Account number or IBAN, SWIFT / BIC) or Something else, with What it is and Where to send it.
  5. Under Numbering & tax, set their own invoice series (Invoice number prefix, Next number), Tax % and a Tax note.
  6. Under Contract, set Contract no., Under contract since, Payment terms (days), What is supplied and the Engagement manager, who accepts their months.
  7. Choose Add contractor. The app says Contractor added. The person now has My Month in their menu.

The contractor can fill in and change their own legal entity, payment details and numbering later, under My Month → Billing details. The contract, the engagement manager included, is never theirs to change. Someone in Finance can edit everything on a profile except the engagement manager. Adding the profile also turns off Paid holidays on the person's page under People, because a contractor is paid for the hours they log, not for the organization's holidays. An administrator can turn it back on there (see Holidays).

2. Set what they are paid

A contractor's pay rate is their cost on Team costs, not a field on the profile, so a raise from a date prices the days after it and leaves the days before alone. Finance or an administrator adds a cost period for them:

Every recorded day in the month is on the protocol, whatever the project or activity, internal work included. A day no cost period covers cannot be submitted until one is added.

3. Confirm where the money goes

Before a month can be approved for payment, someone in Finance or an administrator has to have looked at where the money is going. Whoever saves a change to the payment details, the contractor included, clears the confirmation, and both screens warn about it before you save.

  1. On Profiles, a contractor whose details need it shows Not confirmed under Paid by, with Confirm payment details.
  2. Choose Confirm payment details. The dialog shows the account, or the other payment option, in full. Check every character against what the contractor told you, not against the screen.
  3. Choose Confirm payment details again. The app says Payment details confirmed for …., and the confirmation is written onto the history of each month it clears for payment.

Finance and administrators can confirm. A contractor who is neither cannot.

Your month, as a contractor

This section is the contractor's part, start to finish. My Month itself is described in My Month.

  1. Record your hours through the month on My Week or My Day. You can submit your weeks as you go, or leave them for the month.
  2. Open My Month in the menu, under My time. It opens on this month; use ‹ to go back to the one you are closing. Until you submit, the protocol and the invoice are a preview: Preview only — nothing has been sent. Figures follow your timesheet until you submit.
  3. Clear the checks under Before you submit. For workdays with no time, choose Log time to record it, or Mark as not worked. For missing billing details, choose Complete details. A missing rate is for Finance to add (step 2).
  4. Choose how the invoice is drawn under Invoice source: a number from your own series, or I issue my own with your invoice's number and total, and how detailed the protocol's lines are.
  5. Choose Submit. It is disabled until every check that blocks submission passes. Submitting submits any of the month's weeks still open, freezes both documents and sends them to your engagement manager. The app says Submitted for countersigning., the month says Awaiting sign-off, and your engagement manager is emailed.
My Month for September 2026 as Tomas Lindqvist sees it, marked Awaiting sign-off, with protocol AP-202609-TL accepted by Priya Raghavan. The acceptance protocol on the left lists three tasks at $81.00 an hour, 62.5 hours accepted for $5,062.50. On the right, This month shows the total and five filings, all Pending. Before you submit is Ready: every workday is accounted for, a warning that 5 filings are not yet approved and are approved when the month is countersigned, and the details, rate, invoice number LSW-007 and payment confirmation are all on file. Below, 12 days are marked as not worked, and Withdraw, with a note that nobody has acted on the month yet.
A submitted month, waiting for the engagement manager. Until they act, you can still withdraw it.

After that, the month moves on without you: Awaiting sign-off, then With accounting once it is countersigned, Approved to pay, and Paid. Its History says who did what, and when.

4. Countersign the month

For the engagement manager, an administrator, or someone in Finance allowed to countersign. The number beside Contractors in the menu counts the months waiting for you to countersign.

Tomas Lindqvist's September 2026, AP-202609-TL, as Priya Raghavan, his engagement manager, sees it, marked Awaiting sign-off. On the left, the Acceptance protocol tab: provider Lindqvist Software AB, client Vayner Systems Ltd, contract ATL-SUB-07, 62.5 hours, and three tasks at $81.00 an hour for $5,062.50. On the right, This month shows the total and five filings, all Pending; Decide has Countersign protocol, with a note that accepting the month also approves every filing of it nobody has signed off, and Return to contractor; Payment begins with the payee and bank account.
The month as its engagement manager opens it from the register.
  1. Choose Contractors in the menu. The register opens on the current month, with the months waiting for you first; use ‹ to go back to the month being closed.
  2. Choose the contractor's name. The month opens with its Acceptance protocol and Invoice tabs, and beside them its figures, its Filings (the weeks in it and whether they are approved), its Checks and its History.
  3. Check the work performed, then choose Countersign protocol. There is no confirmation. The app says Month countersigned.

Countersigning also approves every week of the month that nobody had approved yet, exactly as approving them on Approvals would, so there is nothing left for that contractor's month in the approvals queue. The month says With accounting.

If the month is wrong, send it back instead (below).

5. Approve it for payment

For Finance and administrators. Approving is accounting's decision that the month will be paid, and it puts the month in the next payment run.

Tomas Lindqvist's August 2026, AP-202608-TL, for a Finance user, marked With accounting, with Months, Awaiting payment and Profiles at the top. The protocol shows 7 hours on Dispatch API at $81.00 for $567.00, accepted by Priya Raghavan. On the right, This month lists six filings, all Approved; Decide has Approve for payment and Return to contractor; Payment shows the payee, SEB and the account number.
A countersigned month, with accounting.
  1. On Contractors, Finance and administrators see the months With accounting first. Choose the contractor.
  2. Check the Payment panel: the payee, where the money goes, the amount and the Due date, which is the invoice date plus the contract's payment terms. It should say Payment details confirmed on ….
  3. Choose Approve for payment. The app says Approved for payment., and the month says Approved to pay.

Approving is refused while the payment details are unconfirmed. The panel says so first: Nobody has confirmed where this money goes, so it cannot be approved for payment., with Confirm payment details, which opens Profiles.

6. Pay it and record it

For Finance and administrators. Clock Clerk does not move money: you pay through your bank, then record it.

The Contractors register for July 2026, for a Finance user, saying Nothing to approve this month, with a link reading Awaiting payment (3 · $7,452.00) beside the month. The tiles show 1 / 1 submitted, 0 awaiting sign-off, 0 with accounting, $1,822.50 approved to pay with an Export 1 to payment file button, and 0 with the contractor. Tomas Lindqvist's row has AP-202607-TL, invoice LSW-005, 22.5 hours, $1,822.50, submitted August 1, due August 14, Approved to pay. Below, How a month closes lists the four steps.
A month approved to pay, ready for the payment file.
  1. Take the payment file, if you pay by bank import. On the register, for the month in view, the Approved to pay tile offers Export … to payment file. It downloads a CSV named for the run, such as PAY-20261022-0930.csv, with a line per month approved and not yet in a file: Payee, Account, SWIFT, Amount, Invoice number, Protocol number, Due date, Payment method and Payment details. For a contractor paid some other way than a bank transfer, Account and SWIFT are empty and the last two say how. Each month in it then says in the payment file, and the tile says Payment file up to date, so a month never goes into two files. Months your ERP pays as vendor bills say sent to … instead and are never in the file.
  2. Pay the contractor through your bank, from the file or by hand.
  3. Record it. Open the month and choose Mark as paid. Set Paid on, the day the money left (not before the month, and not in the future), and the Reference from your bank statement, which is required. Choose Record payment. The app says Recorded as paid.
The Mark as paid dialog over Tomas Lindqvist's July 2026, for a Finance user. It says AP-202607-TL claims $1,822.50 from Lindqvist Software AB, due August 14, 2026. Paid on is October 22, 2026 and Reference is SEB-20261021-0447, with the note Lindqvist Software AB is recorded as paid in full. Cancel and Record payment are below.
Recording the money going, with the reference off the statement.

The month says Paid, and nothing on it is left to decide. Taking the payment file does not mark anything paid: each month still needs Mark as paid.

Awaiting payment, at the top of Contractors, lists every month submitted and not yet paid, whichever month it is for, oldest due first: a total per state, and each claim's Due date and how many days it is overdue. Download CSV saves the list. See Contractors.

Sending a month back

The Return to contractor dialog over Tomas Lindqvist's September 2026, as Priya Raghavan sees it. It says AP-202609-TL goes back to Lindqvist Software AB for changes, the hours behind it are released so they can be corrected and the month resubmitted, and the number it already carries is kept. What has to change reads The 14th is booked to the wrong project., with a note that a reason is required. Cancel and Send it back are below.
Sending a month back. The reason is required, and the contractor is emailed it.
  1. On the month, choose Return to contractor. It is there while the month is Awaiting sign-off or With accounting, for the engagement manager, Finance and administrators.
  2. Under What has to change, say what is wrong. The reason is required.
  3. Choose Send it back. The app says Sent back to the contractor.

The month says Returned, the contractor is emailed the reason, and its hours are released from the protocol. A countersigned month loses its countersignature, so it has to be accepted again after it is resubmitted. The weeks themselves are not reopened: weeks the countersignature approved stay approved, and the person who reviews them reopens one on Approvals if its hours have to change.

A month Approved to pay or Paid cannot be sent back.

Reminders and emails

The app emails three things, when your deployment can send email:

Where there is no way to email the person, the button reads Mark as reminded: the nudge goes onto the month's history and nothing is sent. The month's History lists every email with what became of it.

What the contractor lock freezes

Submitting puts every day of the month on its acceptance protocol, and the contractor's claims for the month that they paid for themselves go on it too (see Contractors' expenses). While they are on it, they cannot change:

The lock lifts by itself when the month is withdrawn by the contractor or sent back by a reviewer. Once the month is Approved to pay or Paid, nothing lifts it: the app says …, which has been approved for payment. They are final. (or which has been paid).

The locks are asked in order: the invoice, then the protocol, then the week. An hour can be on a client's invoice and on a contractor's protocol at once, which is normal: the client is billed for it and the contractor is paid for it. To change such an hour:

  1. Finance voids the invoice, or removes the hours from a draft (Why billed hours are locked). Until then the app names the invoice, not the protocol.
  2. The protocol is withdrawn by the contractor or sent back by a reviewer, while it can still be.
  3. The week is reopened, by the contractor or by their reviewer, and corrected (Why a week cannot be edited).

When something goes wrong