FlowRunner
PricingContact
Theme
Start Free

PowerOffice Go

Accounting

PowerOffice Go is the Norwegian cloud accounting platform. Agents manage customers, suppliers, and products, invoice sales orders, post vouchers to the general ledger, and read the customer and supplier sub ledgers, projects, and departments.

52 actions OAuth available
PowerOffice Go website Platform Documentation Capability data verified 2026-08-24
A scheduled poll finds sales orders that are ready to invoice
Get Sales Order with its lines returns the complete order rather than the header alone
List VAT Codes and List General Ledger Accounts confirm every line names identifiers the client actually holds
Get Lock Date confirms the posting date is not inside a period that has already been closed
Send Sales Order Invoice turns the order into a sent invoice, which books it to the general ledger
Get Sales Order Send State reports the outcome of the queued send and the agent posts the result
A controller approves any correcting entry before it reaches the ledger, rather than the agent posting it directly

What This Integration Enables

PowerOffice Go draws a hard line between a document and a booking. A sales order carries the customer, the lines, and the attachments, and none of it touches the general ledger until Send Sales Order Invoice turns it into an invoice. Customer prospects work the same way: they live in their own register with no sub-ledger account until Convert Prospect To Customer promotes them. That separation is what makes the platform safe to automate at volume, because an agent can do all of the assembly in a place where mistakes are still editable.

FlowRunner agents maintain the customer, supplier, and product registers, build sales orders line by line with their attachments, invoice them, and follow the queued send to its outcome. They post to the general ledger, read the trial balance and both sub-ledgers, and attribute revenue and cost to projects, departments, and custom dimensions. PowerOffice publishes no webhooks and says so plainly, so nothing here pretends to listen for events. Every listing carries the changed-since and created-since filters the vendor recommends polling with, and the general ledger has something better: corrections in Go produce new reversal vouchers rather than modifying existing ones, so an incremental sync on voucher number never has to revisit what it already holds.

Without FlowRunner

Draft and booked look alike Whether something has been invoiced is a question someone answers by opening it
Period closes discovered late A posting into a closed period is found during review rather than before the write
Corrections posted straight in A fix goes into the ledger with no second pair of eyes and leaves a permanent counter-entry

With FlowRunner

The draft stage is used as a draft Sales orders carry the whole document while nothing is booked, and the send is the moment of commitment
The lock date is read first The agent asks what is closed before it proposes a posting date
Corrections take the approval route Entries are built, balanced, and submitted for approval instead of written directly to the ledger

Use Case Scenarios

  • Orders become Norwegian invoices with their paperwork attached

    An order completes in Shopify or is confirmed in a CRM record in HubSpot. The agent resolves the buyer with List Customers, creating it through Create Customer when it is genuinely new, and builds the document with Create Sales Order and Create Sales Order Line. Add Sales Order Attachment files the signed order confirmation so it travels with the invoice. Nothing is booked yet. When the fulfillment system confirms delivery, Send Sales Order Invoice queues the invoice and Get Sales Order Send State reports whether it actually went.

  • A sub-ledger review that runs itself

    Every Monday the agent calls Get Customer Ledger for open items and Get Supplier Ledger for what is owed out, then Get Trial Balance for the closing position behind both. It writes the movements into Google Sheets and posts a summary to Slack naming the accounts that moved most and the customers whose open items aged past terms. Because List Account Transactions is filtered on voucher number, the sync is incremental and the same transaction is never counted twice.

  • Project profitability that stays current

    Revenue and cost are attributed through projects, departments, and custom dimensions rather than through a separate reporting tool. The agent calls List Projects and List Departments to read the current dimension set, creating a project with Create Project when a new engagement is opened upstream. It then pulls List Account Transactions filtered to those dimensions and pushes per project revenue and cost into the reporting sheet the leadership team already reads. When a project has cost but no revenue for two consecutive periods, the agent flags it rather than closing it.

Human-in-Loop Highlight

PowerOffice Go has two doors into the general ledger, and the difference between them is the whole reason this gate exists. Post Voucher writes straight in. The posting is immediate, and the only way back is Reverse Voucher, which adds a counter-entry while the original stays in the ledger, because that is what the accounting rules require. The other door is a journal entry voucher draft: editable while it is a draft, removable with Delete Voucher Draft, and reaching the ledger only after Submit Voucher For Approval puts it in front of a person. Same numbers, two permanences. So the agent does the work and takes the second door. It builds the entry, adds the lines up locally and refuses an unbalanced voucher with the actual total, reads Get Lock Date to confirm the period is still open, and resolves every account against List General Ledger Accounts and every VAT identifier against List VAT Codes. Then it submits for approval and posts what it found, including the specific line it was least sure of. That last check matters more than it looks: a voucher line names a VAT identifier rather than a percentage, and a wrong one misreports the VAT return rather than just the amount on the entry. A person approves. The agent handles everything either side.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

52 actions

Customers and Prospects

6
  • List Customers Lists the customers or the customer prospects of the client. A prospect lives in its own register until it is promoted.
  • Get Customer Reads one customer or customer prospect by its identifier.
  • Create Customer Creates a customer or customer prospect. A company needs a name and an organization number, and a private individual needs Is Person set with a first and last name.
  • Update Customer Updates a customer or customer prospect. Only the fields supplied are changed, so enrichment passes are safe.
  • Convert Prospect To Customer Promotes a customer prospect into a real customer, which is what gives it a sub-ledger account. The moment a pipeline record becomes an accounting one.
  • Delete Customer Deletes a customer or prospect. PowerOffice refuses when it has ledger activity, in which case archiving it is the alternative.

Suppliers and Contacts

6
  • List Suppliers Lists the suppliers of the client.
  • Get Supplier Reads one supplier by its identifier.
  • Create Supplier Creates a supplier. A company needs a name and an organization number, and a private individual needs Is Person set with a first and last name.
  • Update Supplier Updates a supplier. Only the fields supplied are changed.
  • List Contact Persons Lists the contact persons attached to a customer or supplier.
  • Create Contact Person Adds a contact person to a customer or supplier, which is who an invoice can name as the buyer's reference.

Sales Orders

10
  • List Sales Orders Lists the sales orders of the client. A sales order is the invoice draft, and nothing is booked until it is sent.
  • Get Sales Order Reads one sales order. The plain read returns the header only, so Include Lines is what fetches the complete order.
  • Create Sales Order Creates a sales order complete with its lines. This is the invoice draft, and it stays editable until it is invoiced.
  • Update Sales Order Updates the header of a sales order. Only the fields supplied are changed, and the lines have their own operations.
  • Delete Sales Order Deletes a sales order. Only an order that has not been invoiced can be removed.
  • Create Sales Order Line Adds a line to an existing sales order, which is how an agent builds a document incrementally.
  • Delete Sales Order Line Removes a line from a sales order.
  • Send Sales Order Invoice Turns a sales order into a sent invoice, which books it to the general ledger. It queues a send request rather than sending synchronously.
  • Get Sales Order Send State Reads the send state of sales orders, which is how a queued invoice send is followed up rather than assumed.
  • Add Sales Order Attachment Attaches a file to a sales order by fetching it from a URL, so the supporting document travels with the invoice.

Invoices

3
  • List Outgoing Invoices Lists the sent outgoing invoices and credit notes. The listing carries headers only, so line detail is a separate read.
  • Get Outgoing Invoice Reads one outgoing invoice or credit note. Include Lines fetches its line detail, which PowerOffice warns may be incomplete for an invoice imported rather than issued from Go.
  • List Incoming Invoices Lists the posted supplier invoices and credit notes. These are lightweight records without their cost lines, so List Account Transactions is what returns the full voucher.

Products

6
  • List Products Lists the products of the client, which carry the sales account, unit price, and unit a sales order line inherits.
  • Get Product Reads one product by its identifier.
  • Create Product Creates a product. A price or sales account left empty is inherited from the product group rather than left unset.
  • Update Product Updates a product. Only the fields supplied are changed.
  • Delete Product Deletes a product. Archiving it is the alternative once it has been used on documents.
  • List Product Groups Lists the product groups, which supply the defaults a product inherits.

Dimensions

6
  • List Projects Lists the projects, which are the dimension revenue and cost are attributed to for per project reporting.
  • Create Project Creates a project, which document lines and time transactions can then be attributed to.
  • Update Project Updates a project. Only the fields supplied are changed.
  • List Departments Lists the departments, which are the reporting dimension most document lines carry.
  • Create Department Creates a department.
  • List Custom Dimensions Lists the custom dimensions, which are the three extra reporting dimensions beyond department and project.

Ledger Reference

5
  • List General Ledger Accounts Lists the chart of accounts, which is what every voucher line references.
  • List VAT Codes Lists the VAT codes. A voucher line names the VAT identifier rather than a percentage, and this is where those identifiers come from.
  • List Currencies Lists the currencies active on the client, which is what a document's currency code has to be one of.
  • Get Financial Settings Reads the financial settings, including the conversion date before which nothing can be posted.
  • Get Lock Date Reads the accounting lock date. Nothing can be posted on or before it, so reading it first is how a flow avoids posting into a closed period.

Vouchers

5
  • Post Voucher Posts a voucher straight to the general ledger. The posting is immediate and can only be undone with a counter-entry, which is why this page holds it behind a person.
  • Reverse Voucher Reverses a posted voucher by writing a counter-entry. The original stays in the ledger, which is what the accounting rules require.
  • List Journal Entry Vouchers Lists the journal entry voucher drafts. Unlike a posted voucher these are editable until they are approved.
  • Submit Voucher For Approval Submits a journal entry voucher draft for approval, which is the step before it reaches the ledger. The route an agent takes by default.
  • Delete Voucher Draft Deletes a journal entry voucher draft along with its lines and pages. A voucher already in the ledger is reversed instead.

Reports and Sub-Ledgers

4
  • List Account Transactions Lists the general ledger transactions between two dates. Corrections produce new reversal vouchers rather than changing existing ones, so an incremental sync on voucher number is safe.
  • Get Trial Balance Reads the trial balance at a date, which is the closing position of every general ledger account.
  • Get Customer Ledger Reads the customer sub-ledger. Balances gives what each customer owes at a date, Open Items the unsettled invoices behind it, and Statement every movement between two dates.
  • Get Supplier Ledger Reads the supplier sub-ledger. Balances gives what is owed to each supplier at a date, Open Items the unsettled bills behind it, and Statement every movement between two dates.

Account

1
  • Get Client Information Reads the client this connection reaches, which is the quickest way to confirm the keys point at the right company before anything is written.

Frequently Asked Questions

What can FlowRunner do with PowerOffice Go?

FlowRunner agents can run List Customers, Get Customer, and Create Customer in PowerOffice Go, plus 49 more actions.

Does connecting PowerOffice Go to FlowRunner require OAuth?

Yes. PowerOffice Go connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can PowerOffice Go trigger a FlowRunner workflow automatically?

PowerOffice Go doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with PowerOffice Go

Free plan, no card required. Connect in minutes.