> For the complete documentation index, see [llms.txt](https://docs.younium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.younium.com/erp-and-accounting-integrations/power-office-go.md).

# PowerOffice Go

## Synchronisation scope

| Synchronisation           | Direction                | When it runs                                                        |
| ------------------------- | ------------------------ | ------------------------------------------------------------------- |
| Invoices and credit notes | Younium → PowerOffice Go | When an invoice is posted in Younium, if invoice posting is enabled |
| Accounts                  | Younium → PowerOffice Go | On demand from the integration settings, or as a scheduled job      |
| Accounts                  | PowerOffice Go → Younium | On demand from the integration settings, or as a scheduled job      |
| Products                  | PowerOffice Go → Younium | On demand from the integration settings                             |
| Currencies                | PowerOffice Go → Younium | On demand from the integration settings, or as a scheduled job      |
| Chart of accounts         | PowerOffice Go → Younium | On demand from the integration settings                             |
| Payment terms             | PowerOffice Go → Younium | On demand from the integration settings                             |

Not in scope: exchange rates, payments, journals.

***

## Overview

PowerOffice Go integration synchronises customers, products, currencies, chart of accounts, and payment terms, and posts outgoing invoices to PowerOffice Go when Younium invoices are posted. The integration uses the PowerOffice Go SDK with OAuth client credentials (application key + tenant client key). Posted invoices are saved as drafts then sent; order number and ids are written back to Younium custom fields.

***

## Authentication

You connect PowerOffice Go with a client key, which you generate in PowerOffice and paste into the integration settings along with the PowerOffice environment to connect to. Younium validates the key against PowerOffice when you activate.

From then on Younium manages its own access, renewing it as needed, so the connection stays live without intervention. Younium also paces its requests to stay inside PowerOffice's rate limit, so a large batch of invoices takes longer to send rather than failing partway.

***

## Activation and deactivation

Activating validates the client key against PowerOffice.

Saving the settings prepares Younium for posting: it creates the custom fields the integration maps to, the invoice delivery method list on accounts, and turns on invoice posting when you have enabled it.

Deactivating clears the settings and stops invoice posting; documents already in PowerOffice are untouched.

***

## Custom fields

| Entity                              | Custom field name                         | Notes                  |
| ----------------------------------- | ----------------------------------------- | ---------------------- |
| Account                             | `PowerOffice Go Customer Number`          | Required on post       |
| Account                             | `PowerOffice Go Customer Id`              | Sync                   |
| Account                             | `Power Office Go Invoice Delivery Method` | List                   |
| Product, Charge, OrderProductCharge | `PowerOffice Go Product Code`             | Line product code      |
| Invoice                             | `PowerOffice Go Invoice Id`               | After post             |
| Invoice                             | `PowerOffice Go Invoice Number`           | Order number from POGO |

Renaming breaks integration lookups.

***

## Eligibility and filtering

* Both customer number and customer id custom fields must exist on account.
* Each line must resolve product code on charge (fallback to order product).
* Lines ordered by charge number; `ApplyZeroAmountFilters`.
* Accrual (`UseAccrual`): only non–one-off lines with `MonthlyRecognitionOverTime`; deferred/recognised revenue **codes must be numeric** for balance/result accounts.

***

## Field mapping — posted invoice (Younium → PowerOffice Go)

### `OutgoingInvoice` header

| Younium field                       | PowerOffice Go field   |
| ----------------------------------- | ---------------------- |
| Customer number custom field (long) | `CustomerCode`         |
| `Subtotal.CurrencyCode`             | `CurrencyCode`         |
| `YourReference`                     | `CustomerReference`    |
| `InvoiceDate`                       | `OrderDate`            |
| `YourOrderNumber`                   | `PurchaseOrderNo`      |
| `InvoiceDate`                       | `DeliveryDate`         |
| `PaymentTerm`                       | `PaymentTerms`         |
| `ExchangeRate`                      | `CurrencyExchangeRate` |

### `OutgoingInvoiceLine`

| Younium field                                          | PowerOffice Go field                            |
| ------------------------------------------------------ | ----------------------------------------------- |
| Product code custom field                              | `ProductCode`                                   |
| Description + service period                           | `Description`                                   |
| Qty from line quantity or 1; unit price = subtotal/qty | `Quantity`, `UnitPrice`                         |
| `MapDiscount` + charge discount logic                  | `DiscountPercent`                               |
| —                                                      | `LineType` = `Normal` or `Text` for notes       |
| Accrual settings + revenue accounts                    | `Accrual` (balance/result codes, from/to dates) |

### Write-back (Younium)

| PowerOffice Go field                | Younium field                                                    |
| ----------------------------------- | ---------------------------------------------------------------- |
| Draft/sent invoice id and `OrderNo` | **PowerOffice Go Invoice Id**, **PowerOffice Go Invoice Number** |

Flow: save draft → optional send → on send failure may delete draft; entity log “Sent to PowerOffice Go”.

***

## Post invoice workflow

**Runs when:** an invoice is posted in Younium.

Younium sends one invoice at a time to PowerOffice Go for each customer account, even when many invoices are posted in parallel. The others wait their turn, up to five minutes, so a large batch takes longer rather than being rejected.

If PowerOffice Go still rejects a save because of a concurrent update on its side, for example when an invoice is posted manually at the same moment, Younium retries it up to three times, waiting about one, two and four seconds between attempts. Ordinary validation errors, such as a missing product code or an unknown customer, are not retried and fail immediately. If the last retry fails, the invoice is reported as failed in the same way as any other rejected invoice.

***

## Import / export jobs

Import accounts, currencies; export accounts; synchronise products, chart of accounts, payment terms via service methods/jobs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.younium.com/erp-and-accounting-integrations/power-office-go.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
