BrickiePricingDocs
BrickieDocsSign in
All documentation

Start here

Getting started

From an empty account to a subcontractor paid at the authorised net. Most of the work is one-off setup; after that a payment takes a couple of minutes.

On this page

Before you start

Three things have to exist outside Brickie first.

  • An active ROS digital certificate, downloaded as a .p12 file, and its password. This is the same certificate you use to log in to ROS. If you only ever sign in to ROS with a username and password in a browser, you may not have downloaded the certificate file itself — see Your ROS certificate.
  • Registration as a principal contractor for RCT, with your registration number to hand.
  • A business bank account that accepts uploaded SEPA payment files. Brickie produces the file; your bank moves the money.

One-off setup

  1. 1

    Create your company

    Sign up and give your company a name and RCT registration number. Everything you record belongs to that company and is invisible to every other company on Brickie.

  2. 2

    Import your certificate

    On the Certificate page, choose your .p12 file and enter its password. It is encrypted and stored in your browser, and never sent to Brickie. You will unlock it once per session.

  3. 3

    Add your subcontractors and suppliers

    On Subcontractors, add each one and mark whether they are a subcontractor, a supplier, or both. Enter bank details from something you trust — a signed onboarding form or a phone call to a number you already had — rather than from an invoice. Why this matters.

  4. 4

    Set up your projects

    Optional, but this is what makes cost reporting useful. Invoices with no project still count, they just group under “Unassigned”.

Your first payment

  1. 1

    Record the invoice

    On Invoices, enter the invoice and assign it to a project. A subcontractor invoice within RCT scope should carry no VAT.

  2. 2

    Notify the contract

    The first time you file for a subcontractor, Brickie notifies the contract to Revenue and stores the contract ID and SIN it returns. You do this once per contract, not once per invoice.

  3. 3

    Notify the payment

    Brickie sends the gross amount to Revenue and gets back the Deduction Authorisation — the rate, the amount to withhold and the net to pay. This takes a couple of seconds and needs your certificate unlocked.

  4. 4

    Build a pay run and download the file

    On Pay run, select the authorised payments and download the SEPA file. Only payments with a valid authorisation can be included.

  5. 5

    Upload it to your bank and authorise

    Upload the file in your bank’s online banking and authorise it the way you normally would. Brickie has no access to your account and cannot do this part.

There is a delay after notifying a contract

A newly notified contract is not immediately usable for payment notifications — Revenue’s systems take a short while to catch up, and a payment notification sent too early is rejected with cannot find details for contract. Brickie retries for you. The delay is variable, so if you know a payment is coming, notify the contract before you need it rather than on the day.

What it looks like afterwards

After the first setup, the recurring work is step one to five above, and steps two and three collapse into one action for a contract that already exists. Recording an invoice and getting an authorisation is roughly a minute.

Two things are worth doing periodically rather than daily: checking against Revenue to confirm your filings actually landed, and looking at costs to see where a job stands.