Day to day
Paying subcontractors
Brickie produces a SEPA payment file at the authorised net. You upload it to your bank and authorise it. Brickie holds no banking credentials and cannot move money.
On this page
Building a pay run
On Pay run, select the payments to include and download the file. Only payments carrying a valid Deduction Authorisation can be selected, and each is included at the net Revenue authorised — never at the invoice amount.
The file total is what leaves your account. The withheld amounts are not in the file — they are remitted to Revenue separately as part of your RCT return.
What stops a payment
| Reason | What to do |
|---|---|
| No Deduction Authorisation | File a payment notification first. Paying without one makes you liable at 35% regardless of the subcontractor's actual rate. |
| Bank details differ from the invoice | Resolve it through the change process, with a callback. Do not edit the invoice to match. |
| No bank details on the subcontractor | Add them from a trusted source — not from the invoice. |
| A pending bank detail change | Wait for it to complete. Payments are held rather than sent to the old account. |
| Invalid IBAN | The checksum does not pass, so it is a typo or a corrupted paste rather than a real account. |
The block on missing authorisations is not a warning
It cannot be overridden, because the thing it prevents has a fixed price. Pay €10,000 without an authorisation and you can be liable for €3,500 of it yourself, even where the subcontractor was at 0% and nothing was actually due.
The payment file
The file is a SEPA credit transfer instruction in the pain.001.001.09 format — the standard Irish and European banks accept for bulk payments. It contains your account, each subcontractor’s account, the amounts, and a reference per payment.
- It is an instruction, not a payment. Nothing moves until your bank has it and you have authorised it.
- It contains bank details. Treat the downloaded file the way you would treat a signed cheque book.
- Each payment carries a unique reference so it can be matched back when your bank reports on the file.
Uploading it to your bank
- 1
Find the bulk payment upload
In your online banking, this is usually under payments or file upload. The exact wording differs by bank.
- 2
Upload the file and check the total
Your bank will show the number of payments and the total before you authorise. Check both against what Brickie showed you. This is the last point at which a mistake is free to fix.
- 3
Authorise
With your Digipass or whatever your bank uses. Only you can do this.
Your bank may want a few details first
Some banks require a registration step before they accept uploaded payment files, and may issue you an originator identifier to include. If your bank asks for one, add it in Brickie and it will be included in future files. This is a one-off.
After the bank has it
Mark the file as submitted in Brickie so the payments are not offered again in the next pay run. If your bank provides a status report for uploaded files, Brickie can read it and match any rejected payments back to the ones they came from — a payment your bank refused is one you still owe.
A bank rejection does not undo the RCT filing. The deduction was authorised and the notification stands; what failed is the transfer. Fix the bank detail problem and pay it — do not re-notify.
Why not just pay directly
Brickie could have connected to your bank and moved money. That was looked at and rejected, for a reason worth knowing since it explains the extra upload step.
- It would mean holding credentials to your operating account. The strongest thing Brickie can say about payment security is that it holds nothing capable of moving your money. That is only true while it stays true.
- The available routes did not fit. The payment providers that could have been used are either unavailable for this purpose in the EU, require a partnership Brickie does not have, or are not offered in Ireland. Holding balances directly needs a licence.
- Builders were wary of it anyway. Granting any access to the main operating account is the thing the intended users of this product were most reluctant to do.
The cost is one upload per pay run. The benefit is that no compromise of Brickie, at any scale, can result in money leaving your account.