Creditcrest Credit Reporting
Comprehensive credit reporting straight from the ledger, every condition checked first.
Report from the ledger.
Monthly repayment history and hardship information, reported from the ledger.
What you do here. See an example ledger reported as monthly repayment history and hardship information, each default condition checked.
Try it end to endTake the tour- You bring
- The LoanManager ledger
- You get
- Monthly repayment history and hardship information
- Holds the line
- Every s 6Q condition checked before a default
Managed for you
Example Lending, an invented lender, as at 29 Sept 2026.
1 overdue. Next due: September 2026 contribution, 10 Oct 2026.
- August 2026 contribution — correction
Due 8 Sept 2026 Overdue Awaiting approval - September 2026 contribution
Due 10 Oct 2026 Month not ended
3 credit enquiries this month. Each is logged with who asked, when and for which application. Never the report.
How it works
- The lender holds the agreement with its credit reporting body. We hold no account of our own.
- Each month we prepare repayment history from the ledger and check it. Account details come from the lender’s own system.
- A named person at the lender approves it: not whoever prepared or checked it, and never us.
- We send it on the lender’s own credentials, or the lender lodges it.
- A real body is connected from its own specification, which comes with the lender’s agreement. Today only the sandbox is.
- A rejection becomes a correction, with its own due date.
Each filing, step by step
August 2026 contribution — correction — Awaiting approval. Due 8 Sept 2026: 5 days after the body’s rejection of 3 Sept 2026, under the agreement.
- 1 Sept 2026: prepared by Creditcrest
- 1 Sept 2026: checked by Creditcrest
- 2 Sept 2026: approved by Cy (compliance)
- 2 Sept 2026: submitted by Creditcrest
- 3 Sept 2026: rejected by the body
- 7 Sept 2026: prepared by Creditcrest
- 7 Sept 2026: checked by Creditcrest
Flagged Overdue: the correction fell due on 8 Sept 2026.
September 2026 contribution — Month not ended. Due 10 Oct 2026: 10 days after the month ends, under the lender’s agreement with the body.
July 2026 contribution — Acknowledged. Due 10 Aug 2026: 10 days after the month ends, under the lender’s agreement with the body.
- 3 Aug 2026: prepared by Creditcrest
- 3 Aug 2026: checked by Creditcrest
- 4 Aug 2026: approved by Sam (senior)
- 4 Aug 2026: submitted by Creditcrest
- 4 Aug 2026: acknowledged by the body
Default, LN-ARREARS — Acknowledged. Window closes 25 Aug 2026: no more than 3 months after the s 21D(3) notice of 25 May 2026 (Privacy (Credit Reporting) Code 2025 s 9(1)–(4)); not before 8 June 2026 (Privacy Act 1988 s 21D(3)(d)).
- 15 June 2026: prepared by Creditcrest
- 15 June 2026: checked by Creditcrest
- 16 June 2026: approved by Sam (senior)
- 16 June 2026: submitted by Creditcrest
- 16 June 2026: acknowledged by the body
Repayment history, three example accounts
| Account | 2026-02 | 2026-03 | 2026-04 | 2026-05 | 2026-06 | 2026-07 | 2026-08 |
|---|---|---|---|---|---|---|---|
| LN-CLEAN | C | C | C | C | C | C | C |
| LN-ARREARS | C | 2 | 3 | 4 | 5 | 6 | X |
| LN-HARDSHIP | C | C FHI | C FHI | 2 | 3 | 4 | 5 |
C is current; 1–6 and X are the ages of the oldest unpaid repayment in Privacy (Credit Reporting) Code 2025 s 8(2)–(5). FHI marks a month under a temporary hardship arrangement, where C means kept and 1 means not kept.
Default information — LN-ARREARS on 15 June 2026
Every condition this checks is met. Whether to disclose default information is the licensee’s decision; nothing has been reported.
- ✓ At least 60 days overdue — Oldest unpaid repayment due 1 Mar 2026, 106 days before 15 June 2026. Privacy Act 1988 s 6Q(1)
- ✓ Overdue amount at least $150 — $960.04 of repayments overdue. Account-level fees (dishonour, collection) are not counted toward the threshold here. Privacy Act 1988 s 6Q(1)
- ✓ Written notice of the overdue payment, requesting payment (s 6Q notice) — Given 20 Apr 2026. Privacy Act 1988 s 6Q(1)
- ✓ Not barred by a statute of limitations — Recorded as not barred. Privacy Act 1988 s 6Q(1)
- ✓ Notice of intention to disclose (s 21D(3) notice), separate from and at least 30 days after the s 6Q notice — Given 25 May 2026, 35 days after the s 6Q notice. Privacy (Credit Reporting) Code 2025 s 9(1)–(4)
- ✓ At least 14 days since the s 21D(3) notice — 21 days by 15 June 2026. Privacy Act 1988 s 21D(3)(d)
- ✓ No more than 3 months since the s 21D(3) notice — The window closes 25 Aug 2026. Privacy (Credit Reporting) Code 2025 s 9(1)–(4)
- ✓ No hardship request being decided, or refused less than 14 days ago — No hardship request recorded. Privacy (Credit Reporting) Code 2025 s 9(1)–(4)
Points for your own review
- The symbol for "current" is not fixed by the Code; C is the conventional one.
- A fortnightly or weekly contract is read month by month: the oldest repayment unpaid at month end sets the age.
- A hardship arrangement is tested at month end, not at the later end of any grace period (Code s 8A(3)(b)).
- Whether regulations prescribe a default threshold above $150 (Act s 6Q(1)(d)(ii)) was not checked.
- The registration date of the Privacy (Credit Reporting) Code 2025 was not confirmed on the Federal Register.
Read from the Privacy (Credit Reporting) Code 2025 and the Privacy Act 1988. A lender posts to /v1/credit-reporting: those addresses compute and keep nothing, and send nothing to any credit reporting body. A filing goes only through the service above, once a named person at the lender approves it.