> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcsolar.com.au/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> ## What this documentation covers
> This is the documentation for ArcSolar, the solar-retailer operating system: the web app a solar retailer uses to run quoting, sales, installation, rebates, inventory and reporting. ArcSolar is a hosted web application at https://app.arcsolar.com.au. There is no public API for most workflows, so agentic operation of ArcSolar is UI-driven. Navigate the app, read the labels and controls, and act through the interface, unless a page explicitly documents an API, contract or integration endpoint.
>
> ## How to read these pages
> - Pages are split by audience using Mintlify's Visibility component, and this split is deliberate. Sections marked 'for agents' are hidden on the website and appear only in the Markdown you are reading. They are the authoritative behavioural specification for the page. Where the remaining human-facing prose and an agent section disagree, the agent section is correct.
> - Sections outside any Visibility block appear in both outputs. They are the shared spine of the page: what the feature is and why it matters.
> - Treat every bold label, field name, route, status string and error message quoted in an agent section as canonical. They are copied verbatim from the product. Use that exact wording when telling a user where to click, or when matching an error message to its cause.
> - Australian solar vocabulary is used precisely and not interchangeably: STC (Small-scale Technology Certificate), PRC (Peak Reduction Certificate), REPS, NMI, CEC accreditation, VPP. Do not substitute an overseas equivalent.
> - Money is Australian dollars. Dates shown to users are day-first (DD/MM/YYYY).
>
> ## Behaviour rules for operating or advising on ArcSolar
> - Respect prerequisites and ordering. Agent sections state which inputs block progress and which steps must happen first. Do not skip a step, and do not assume a default that the product itself does not supply.
> - Never invent a value the product requires but the user has not supplied. Ask for mandatory fields rather than guessing. Several features reject a request outright when one is missing, and submissions to external authorities are effectively irreversible.
> - Respect permissions and scoping. Features name the roles, capabilities and access rules that may act. Do not attempt an action the operator's role cannot perform, and do not describe a restricted feature as available to them.
> - Features that are gated, pending release, or blocked on a vendor are documented as exactly that. Never present a gated or unmerged behaviour as live. When availability is unclear for a given workspace, direct the user to support rather than asserting that the feature works.
> - Where a page states something is genuinely undetermined, treat it as unknown. Do not fill the gap with a plausible guess.
> - ArcSolar's supported intelligence tools appear where they help with the task, including bill analysis, call summaries and reporting. Check the underlying evidence. Intelligence does not replace provider approval, verified records or the customer's own confirmation.
>
> ## Getting help
> Support is support@arcsolar.com.au. The customer-facing website is https://www.arcsolar.com.au.

# Grid connections

> Prepare the network application, lodge it in the network's portal and track the outcome.

Every project has a **Grid Connection** tab. ArcSolar works out the electricity network from the NMI and lines up every value and file the network's portal asks for. You still lodge the application in the network's own portal. ArcSolar never sends it for you.

Skip the tab for jobs that don't need a network application.

## Start an application

1. Open the project in [**Projects & Jobs**](https://app.arcsolar.com.au/dashboard/projects).
2. Open **Grid Connection** (under **More** if it isn't shown).
3. Choose **Start application**.

ArcSolar brings across the site, system and documents already on the project. You fill in what's missing.

## Prepare the application

**Prepare application** has three steps.

![The Grid connection tab on the Confirm site step, showing the customer, electricity network, NMI and the Powercor network worked out from the NMI.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/dl-grid-site.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=5aff3a93d4fcf43c0edf4af83e376ade)

Step 1 confirms the supply. The network is worked out from the NMI. Sample data.

**1. Confirm site**

Check the supply address. Enter the **NMI** from the customer's bill; ArcSolar picks the **Electricity network**. You can also choose the network yourself. Choose the **Supply phases** and **Electricity retailer**, tick **I've checked this is the correct supply point**, then choose **Save and continue**.

**2. Check system**

Check the system you're connecting. Choose **Use the system already designed** to bring in the accepted design, or add the equipment. Fill any gaps, such as a missing inverter kVA or battery charge rate. Set the **Requested export**, for example **No export (0 kW)** or **Fixed export limit**.

**3. Review application**

Attach the customer's signed permission and tick **I've reviewed the customer's permission for this application**. Add the reviewed single line diagram. You can reuse the diagram from the Roof Vision design. Check everything, then save.

Use **Technical details** for several meters, a shared inverter or an unusual supply.

> [!TIP]
>
> An NMI from a confirmed bill shows **NMI from confirmed bill**. You're warned if the NMI doesn't match the property's state.

## Fix what's missing

**Updates** shows the **Next action** and a **Before you can lodge** list. Select an item to go straight to the field that completes it.

![The Updates view with the Next action card and a Before you can lodge list of items to complete.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/dl-grid-updates.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=722b72ff6dcb771ed685ecb10d5064e3)

Before you can lodge lists what the network will still need. Select an item to fix it. Sample data.

## Lodge with the network

When the application is ready, the **Lodge with** card shows the network's name.

1. Choose the **Open** button on the card to go to the network's portal.
2. Copy each value across with its copy button, or use **Copy all**. Values include the NMI, address, applicant, panels, inverter kW and kVA, battery size and power, and the export limit.
3. Under **Files to upload**, copy or download the single line diagram, customer permission and site photos.
4. Submit in the network's portal and keep its receipt.
5. Back in ArcSolar, choose **Record submission or decision** and record the submission with its reference and receipt.

Opening the network's site doesn't mark the application as lodged. Only recording the submission does.

## Record the network's response

1. On **Updates**, choose **Record a network update**.
2. Record the response: approval, conditions or a request for more information.
3. Attach the network's decision document and note the approved export limit.

## Close out the connection

**Completion checklist** tracks each outcome on its own: authority, design, conditions, certificate, inspection, metering, commissioning and DER registration.

![The Completion checklist with authority marked required and design, conditions, certificate, inspection and metering not assessed.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/dl-grid-checklist.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=d18a27d5d0b8c8247a1bdbbba35ac1d7)

Each completion item is tracked separately. Sample data.

1. Use **Attach a document** to add evidence from **Project Files**, with its **Document type** and who issued it.
2. Choose **Record the installed system** once installed.
3. Choose **Mark as complete**.

**History** keeps every version you prepared, lodged, had approved or installed, with who changed it and when.

## Find projects that need action

On [**Projects & Jobs**](https://app.arcsolar.com.au/dashboard/projects), choose **Grid attention** to show only projects whose grid connection needs action. Choose **Show all projects** to clear it.

## Properties, NMIs and retailers

A customer can have several properties, each with its own address, NMI, retailer and bill. The project is set up at the property chosen in the quote. An accepted electricity bill fills in a property's NMI and retailer when they're blank.

> [!NOTE]
>
> Grid approval, metering and commissioning are separate from the project stage. Set **Review operations clearance** on the project as each one is done. See [Projects and jobs](https://docs.arcsolar.com.au/delivery/projects.md#work-the-delivery-checklist).

[Continue with**Rebate tracking**](https://docs.arcsolar.com.au/delivery/rebates.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.