AI Grant Funding Administrator · Australia

The money is awarded. The evidence is what still has to line up.

Juno keeps one register of your live grants with the funder, the agreement reference, the funded amount and every milestone and reporting date the agreement names, matches the receipts, invoices and timesheets you supply to the budget lines that agreement sets out, assembles the draft evidence pack each reporting date asks for, and names everything still missing. Your people decide whether a cost is eligible, sign every declaration, and send everything that goes to a funder.

  • Human approval
  • No signing or sending
  • Records in your systems
WORKER / SF/33 AVAILABLE FOR AUDIT
Grant funding administrator

Juno

Every budget line evidenced, or named on the missing list.

ON JUNO'S SHIFT
MON

File the documents that arrived against the grant and budget line they belong to

CHECK
TUE

Draft the internal requests for budget lines still short of a document

APPROVE
THU

Check the assembled packs for budget lines with nothing filed against them

CHECK
FRI

Hand over the missing list and the week's register summary

HANDOFF
MODE HUMAN APPROVALREPORTING ESCALATE

[ THE WEEKLY RECORD ]

Every budget line evidenced, or named on the missing list.

At the end of each week, every live grant on the register shows its next milestone and its next reporting date, every budget line shows the documents you hold against it, every pack assembled has been checked line by line, and every pack that could not be completed carries an explicit list of what it is still missing and who was asked for it.

01

Grant register

Keep one register of your live grants: the funder, the agreement reference, the funded amount, and every milestone and reporting date the agreement names.

02

Budget-line evidence

Match the receipts, invoices and timesheets you supply to the budget lines your funding agreement sets out, as your own records state them.

03

Document checklist

Keep a per-grant checklist of the source documents each budget line still needs, and who was asked for each one.

04

Pack assembly

Assemble the draft evidence pack a reporting date asks for from the documents on file, ready for your authorised person to check.

05

Missing list

Produce the explicit list of what a pack is still missing, with the budget line and the milestone each gap sits under.

06

Date watch

Report every milestone and reporting date before it lands, with the evidence still outstanding against it.

Excluded work: deciding whether a cost is eligible under an agreement, signing or certifying anything, corresponding with a funder or an agency, determining GST treatment, activity statement and PAYG work, and any program sought through the tax system or an income tax return, including the R&D Tax Incentive. Recurring periodic reporting built from source-system data and your own templates stays with Kai, work to win funding before it is awarded with Lena, and the sales ledger with Nora.

[ START WITH ONE WORKFLOW ]

Choose the part of the evidence chain to hand over.

Read access to your funding agreements, your document storage and the accounting records you choose to supply is mapped at onboarding. An email and spreadsheet workflow also works.

WORKFLOW / 01REGISTER

Stand up the grant register

Turn your live funding agreements into one register, each row carrying the funder, the agreement reference, the funded amount and every date that agreement names.

START
Your signed funding agreements and the documents you already hold
DONE
Every live grant listed, dated, and showing what it is still short of
HUMAN
Confirms the budget lines and the dates the register is built against
WORKFLOW / 02EVIDENCE

File the evidence as it arrives

Put each receipt, invoice and timesheet you supply against the budget line it belongs to, and keep the per-grant checklist current.

START
The documents your people supply, and the agreement's own budget lines
DONE
Each budget line showing what is held against it and what is outstanding
HUMAN
Decides whether a cost is eligible and belongs on a budget line
WORKFLOW / 03PACK

Assemble the pack before the date

Build the draft evidence pack a reporting date asks for from the documents on file, with the missing list attached.

START
The register, the reporting date, and the documents held against each line
DONE
A drafted pack and an explicit missing list, ready for a person to check
HUMAN
Reviews the pack, decides eligibility, signs it and sends it

[ THE APPROVAL LANES ]

What Juno does.
What your team decides.

Register and evidence work on documents you supply runs within the agreed scope. Anything that leaves your office, and any change to the register's own structure, waits for a named human. Eligibility, signing, and every dealing with a funder or the tax system sit outside the scope entirely.

GREEN

DOES-IT-ALONE

Internal register and evidence work within the agreed workflow.

  • Keep one register of your live grants with the funder, the agreement reference, the funded amount and the dates that agreement names
  • Match the receipts, invoices and timesheets you supply to the budget lines the agreement sets out, as your own records state them
  • Keep the per-grant checklist of the source documents each budget line still needs
  • Assemble the draft evidence pack from the documents on file, marked as a draft for checking
  • List what a pack is still missing, with the budget line and the milestone each gap sits under
  • Track how long each outstanding document has been waiting, and who was asked for it
  • Compile the weekly register summary of what was filed, what was matched and what is still open
AMBER

APPROVE

A named human approves before anything leaves your office or the register's structure moves.

  • Draft a request to your own staff for a source document that has not arrived, and queue it for a named person
  • Hand an assembled draft pack to your nominated person
  • Add or retire a budget-line mapping in the register
  • Open or close a grant file in your own system
RED

NEVER

Outside Juno's authority, with or without an approval.

  • Decide whether a cost is eligible under a funding agreement
  • Certify, sign or lodge an acquittal, a declaration or a statement to a funder
  • Correspond with a funder, an agency, a department, a Minister or a public sector officer on your behalf
  • Advocate for a funding decision, or act to improve the standing of an application
  • Determine or advise on the GST treatment of an amount
  • Prepare, review or lodge an activity statement, or do PAYG or superannuation work on the funded activity
  • Deal with the Commissioner of Taxation in any form
  • Touch a program sought through the tax system, including anything pursued through an income tax return and the R&D Tax Incentive
  • Move money, or release a payment
  • Hold a credential for a funder portal, a grants portal or a banking portal

[ MINIMUM ACCESS ]

Your funding records stay yours.

The agreements, the receipts, the invoices and the packs live in your systems. Juno works from the copies you forward, or read-only where you grant it, and produces a register, a drafted pack and a missing list for a person to act on. Funding agreements and the evidence behind them often carry third-party personal information, so the records stay in your own storage and Juno never holds a credential for a funder, grants or banking portal.

The load audit uses a blank register, a redacted funding agreement and two or three sample documents. Live data access and retention are mapped during onboarding.

  1. 01

    Map inputs

    Identify the funding agreements, the document storage, the accounting records you will supply and the correspondence record.

  2. 02

    Set access

    Use forwarded copies or read access first; grant a register write only if the agreed workflow needs it.

  3. 03

    Test fictional cases

    Test a budget line with no document against it, a reporting date a fortnight out, and a receipt that names a different period.

  4. 04

    Name approvers

    Name who decides eligibility, who may change a budget-line mapping, and who signs and sends each pack.

[ OPERATING SPECIFICATION ]

Proposed turnaround.
Confirmed at onboarding.

Proposed timings are a source document filed against its budget line on the day it arrives, an internal request drafted within one business day of a gap appearing, a draft evidence pack assembled five business days before its reporting date, and the register summary out each week on the agreed day. The delivery team confirms these against your own agreements and volumes during onboarding.

Example output — fictional grant A
Draft evidence pack assembled five business days before its reporting date
Example output — fictional grant B
Two budget lines short of a document, each named with the person asked
Example output — fictional grant C
Receipt filed against its budget line on the day it arrived
Example output — fictional grant D
Milestone date a fortnight out, reported with the evidence still outstanding
Weekly measures
Documents filed; budget lines matched; packs drafted
Weekly measures
Budget lines short of evidence; requests awaiting a send decision; dates inside the next month
CONTROL / 01ONBOARDING

Start from your own agreements

Set up access, load the live agreements with their budget lines and dates, backfill the documents you already hold, and review the first missing list together.

CONTROL / 02CAPACITY

Size the seat to the agreement list

The delivery team confirms a range of live grants per week per seat, because one agreement with twenty budget lines and quarterly milestones is not the same load as several simple ones. Beyond it, narrow the scope or add a seat.

CONTROL / 03ESCALATION

Surface dated items to a person

Escalate a reporting date approaching with evidence still outstanding, a budget line no supplied document fits, a document that contradicts the register, and anything the confirmed scope does not cover.

CONTROL / 04FUNDER

No route to a funder runs through Juno

Every report, declaration and reply to a funder is made by your own people. Juno assembles and checks what sits behind them, and takes no position on whether a cost is eligible or an acquittal is complete. Where your people have recorded a decision, it sits in the register as a record like any other.

Capacity and turnaround are confirmed during onboarding for your number of live grants, the budget-line detail each agreement sets, the reporting frequency and the day your nominated person reviews.

[ GRANT EVIDENCE LOAD AUDIT ]

Map the evidence chain.

Bring a blank register, a redacted funding agreement and a few sample documents to choose one bounded workflow and its human approvals.

Book the Grant Evidence Load Audit Access is agreed before live work.

[ FROM AUDIT TO TRACKED WORK ]

One workflow.
Named approvers.

STEP 1

Load audit

Review a redacted agreement and choose the first workflow.

STEP 2

Map access

Confirm the budget lines, the dates and where the documents live.

STEP 3

Test fictional cases

Check a line with no document, a date a fortnight out, and a mismatched period.

STEP 4

Review the first pack

Your nominated person checks the missing list, the cadence and the escalation route.

[ BEFORE THE AUDIT ]

Questions about the evidence chain.

Does Juno decide whether a cost is eligible?

No. Juno matches the documents you supply to the budget lines your agreement names, and reports what each line holds and what it is missing. Whether a cost is eligible under the agreement is a decision your authorised person makes, and Juno takes no position on it.

Does Juno sign or certify the acquittal?

No. Juno hands a drafted pack to the person authorised to sign it. Where an agreement requires an audited financial acquittal, the audit is a reserved function held by somebody else: the Community Grants Hub, for example, requires a registered company auditor or a member of CPA Australia, the Institute of Public Accountants, or Chartered Accountants Australia and New Zealand, and your own agreement may name its own or a stricter requirement. Juno is none of those, and never signs, certifies or lodges anything.

Does Juno contact the funder or the agency?

No. Every report, declaration, query and reply to a funder, an agency or a public sector officer is sent by your own people. Juno drafts requests to your staff only, queues them for a named person, and is never presented to a funder as representing you.

Does Juno work on grant applications?

No. Juno starts after an agreement is signed and the money is committed. Nothing Juno does is aimed at a funding decision or at how an application is received. Work before award sits with Lena, and Skillforce does not act for clients in dealings with government.

Is Juno doing bookkeeping or BAS work?

No. Juno takes the amounts in your records as your records state them. Determining or advising on the GST treatment of anything, preparing or lodging an activity statement, PAYG and superannuation work, and any dealing with the Commissioner of Taxation are outside the scope with or without an approval.

What about the R&D Tax Incentive?

Out of scope. Anything sought through the tax system or through an income tax return is excluded, and the R&D Tax Incentive is named so there is no doubt. Juno works on funding administered by a funding agency under an agreement you already hold.

How is Juno different from reporting and analytics administration?

Kai builds your recurring periodic reports from source-system data and your own templates, answering what the numbers say this period. Juno works from the funding agreement itself, its budget lines, milestone dates and conditions, and from the source documents behind them, answering where the paperwork sits for one grant. Different input, different register; which one holds what is set during onboarding.

How is Juno different from estimating and tender administration?

Lena works before award: the pricing pack, the submission register and the deadline. Juno starts once an agreement is signed. Nothing Juno does touches winning the funding.

Which grants system does Juno work in?

Whichever one you already use. The register is a spreadsheet or your existing grants tool, and the documents stay in your own storage. No new system is implied, and Juno never holds a credential for a funder, grants or banking portal.

What happens when a document never arrives?

The budget line stays on the missing list with the document it is waiting on, who was asked for it and how long it has waited, and the gap appears against the milestone it sits under. Juno drafts the internal request and queues it; a named person checks it and sends it.

How is capacity set?

The delivery team confirms a range of live grants per week per seat during onboarding, because one agreement with twenty budget lines and quarterly milestones is not the same load as several simple ones. Above that range, the scope narrows or a second seat is considered.

[ START WITH YOUR OWN AGREEMENTS ]

Know the gap before the date arrives.

Map the live grants, the budget lines and the reporting dates with each approval assigned to a person.

Book the Grant Evidence Load Audit Direct with the founder