Index
What is this integration?
The PC Kasse integration connects the Golfmanager POS with the PC Kasse cash register system. It lets you send Golfmanager sales to PC Kasse to charge them there and, once charged, receive the confirmation back to mark those sales as paid in Golfmanager.
This way, the charge is taken in PC Kasse, but Golfmanager stays always in sync.
PC Kasse is a cash register / point-of-sale system (Norwegian in origin). This integration acts as a bridge: Golfmanager passes it the sale lines and PC Kasse returns the sale already charged.
What problem does it solve?
Charges in PC Kasse without losing control in Golfmanager.
Avoids typing the same sale twice.
Keeps sales in sync: what is charged in PC Kasse is marked as paid in Golfmanager.
Reduces errors in amounts and discounts by transferring the lines automatically.
Which systems does it connect and in which direction does the data flow?
It is a two-way integration between Golfmanager and PC Kasse:
From Golfmanager to PC Kasse: from the POS (opened inside the PC Kasse environment) you send the sale lines (product, quantity, price, discount) to charge them.
From PC Kasse to Golfmanager: after the charge, PC Kasse returns the updated sales and Golfmanager recalculates and marks them as paid with the "Pc Kasse" method.
What information is exchanged?
Information | Direction | Purpose |
Sale lines (product code, description, quantity, price, discount) | Golfmanager → PC Kasse | Charge the sale in PC Kasse |
Updated sales (quantity, price, discount) | PC Kasse → Golfmanager | Recalculate and mark as paid |
Each line carries a reference to the Golfmanager sale, so both systems know which sale it corresponds to.
Prerequisites (before activating the integration)
Have PC Kasse and operate from its environment (PC Kasse WebForm).
Have the PC Kasse module installed, together with the POS and invoicing modules.
A payment method named "Pc Kasse" configured (the module creates it on installation).
The PC Kasse product codes assigned to the products.
How to set it up (step by step)
Step 1 — "Pc Kasse" payment method
Log in to Golfmanager with a user that has billing permission.
Go to Settings > Payment methods.
Check that a method whose name contains "Pc Kasse" exists, configured as a direct payment. (The module creates it automatically on installation.)
If it does not exist, create it or contact support: it is the method that will mark the sales charged in PC Kasse as paid.
Step 2 — Product codes
Go to the record of each product you are going to charge through this channel.
Fill in the "PC Kasse Code" field with the code that identifies that article in PC Kasse.
Save the changes.
⚠️ If a product has no PC Kasse code, a default (generic) code is used. So that each article is identified correctly in PC Kasse, it is best to fill in the code on all the products you sell through this channel.
Explanation of each field
Below is a description of each field in the integration: where it is, what it means, its impact on the system, and a usage example (what happens when it is used and how the system behaves).
A) "Pc Kasse" payment method
Field name: the "Pc Kasse" payment method (in Settings > Payment methods).
Description: the payment means with which sales charged in PC Kasse are marked. It is created automatically when the module is installed, as a direct payment.
Impact on the system: it is essential. When PC Kasse confirms the charge, Golfmanager creates a payment with this method and marks the sales as paid.
Usage example: you make sure it exists and that its name contains "Pc Kasse".
What happens when it is used: when the confirmation is received, the sales become paid with the "Pc Kasse" method.
System behavior: if it does not exist (or is not named so), "The Pc Kasse payment method is not configured" appears and the charge is not recorded.
B) PC Kasse code (on the product)
Field name: "PC Kasse Code" (on the product record).
Description: the code that identifies the article within PC Kasse.
Impact on the system: it travels with each sale line so PC Kasse recognizes the product.
Usage example: on a green fee, you enter its PC Kasse code.
What happens when it is used: the line is sent to PC Kasse with that code.
System behavior: if a product has no code, a default (generic) code is sent and PC Kasse may not identify the article correctly; that is why it is best to fill it in on all of them.
C) Data Golfmanager sends to PC Kasse (on each line)
Field names: article code, description, quantity, price, discount and the sale reference.
Description: for each sale line, Golfmanager sends PC Kasse this data so it can charge it. The reference links the line with the Golfmanager sale.
Impact on the system: it is what PC Kasse uses to display and charge the sale; the reference lets Golfmanager know, on return, which sale it corresponds to.
Usage example: you send a sale with 2 green fees, their price and their discount.
What happens when it is used: PC Kasse displays those lines to charge them.
System behavior: only sales pending payment are sent; the rest are not.
D) Data PC Kasse returns to Golfmanager
Field names: the sale reference, quantity, price and discount.
Description: after the charge, PC Kasse returns for each sale its reference and the final values (quantity, price and discount).
Impact on the system: Golfmanager updates those sales with the received values, recalculates the totals and taxes and marks them as paid.
Usage example: the cashier adjusted a quantity in PC Kasse; on return, Golfmanager recalculates the total.
What happens when it is used: the sale becomes paid with the final values.
System behavior: if a sale no longer exists or is no longer pending, it is not updated (see "Synchronization results").
How to use it day to day (step by step)
In the POS (opened inside the PC Kasse environment), create the sale and select the lines you want to charge.
Click the "Send PC Kasse" button. Only sales pending payment are sent, and they should be for the same customer.
The charge is taken in PC Kasse (the cashier can adjust quantities, prices or discounts).
PC Kasse returns the sales to Golfmanager, which recalculates and marks them as paid with the "Pc Kasse" method.
Review the send result (see the next section) in case any sale was not updated.
Synchronization results
When PC Kasse returns the sales, the result can be:
Result | What it means |
All updated | All sales were marked as paid correctly |
Partial | Some were updated and others were not (for the reasons below) |
None | None could be updated |
Reasons why a sale may not be updated:
Not found: the sale no longer exists in Golfmanager.
Not pending: the sale was already paid or cancelled.
Limitations to keep in mind
It works inside the PC Kasse environment (its WebForm); the send button is only available there.
Only sales pending payment are sent.
Sales sent together should be for the same customer (the payment is attributed to the first sale's customer).
It does not look up members by card nor charge to the member's account: it creates a payment and marks the sales as paid.
There is no reversal/cancellation through this channel: an already-paid sale is cancelled through Golfmanager's normal flow.
It needs the "Pc Kasse" payment method configured and, ideally, the product codes properly assigned.
Frequently asked questions
The "Send PC Kasse" button does not appear.
Sending is only available when the POS is opened inside the PC Kasse environment (its WebForm). If you open Golfmanager in a normal browser, the button does not appear (you will see a notice like "option only valid from the PC Kasse WebForm"). Open the POS from PC Kasse.
It tells me only sales pending payment can be sent.
You selected a sale that is already paid or cancelled. Select only sales pending payment and send again.
"The Pc Kasse payment method is not configured" appears.
There is no payment method whose name contains "Pc Kasse". The module normally creates it on installation; if it is not there, create it (as a direct payment) or contact support. Without it, sales cannot be marked as paid.
A sale was not marked as paid and shows "not found".
That sale no longer exists in Golfmanager (it was deleted). Check the sale's status; if needed, recreate it and send it again.
A sale was not marked as paid and shows "not pending".
The sale was no longer pending payment (it was already paid or cancelled). Review its status in Golfmanager; there is no need to charge it again if it already showed as paid.
The send returned a "partial" result.
It means some sales were marked as paid and others were not, for the reasons above ("not found" or "not pending"). Review the list of those that were not updated and fix each case.
The article is not identified correctly in PC Kasse.
The product's "PC Kasse Code" is usually missing. If a product has no code, a default generic code is sent and PC Kasse may not recognize the article. Fill in the code on the product record.
Does the integration identify the member by their card or number?
No. PC Kasse does not look up members by card or by number. The sale is created in Golfmanager (with its customer) and from there it is sent to PC Kasse to be charged.
Is the amount charged to the member's account?
No. The integration creates a payment with the "Pc Kasse" method and marks the sales as paid; it does not charge to the member's account/credit.
Can I send sales from several customers at once?
It is best to send sales for the same customer. If sales from several are sent, the payment is attributed to the first sale's customer, which can throw off the attribution. Group the sends by customer.
Can I cancel or reverse a charge from PC Kasse?
Not through this channel. Once a sale is paid with "Pc Kasse", its cancellation is handled through Golfmanager's normal billing flow.
Where do the prices and articles come from?
The lines (product, quantity, price, discount) come from the Golfmanager sale. In PC Kasse, the cashier can adjust quantity, price or discount; on return, Golfmanager recalculates the totals and taxes with those values.
Does PC Kasse generate a receipt? And Golfmanager?
PC Kasse generates its own receipt for the charge. Golfmanager, for its part, marks the sale as paid with the "Pc Kasse" method.
Is there a separate test environment?
No. The integration does not distinguish between test and production; it is best to validate the flow with a sample sale before operating normally.
What permission is needed for PC Kasse to confirm the sales?
The call that updates and marks the sales as paid requires billing management permission. Your technical team configures it when connecting PC Kasse with Golfmanager.
Recommended best practices
Assign the PC Kasse code to all the products you are going to charge through this channel.
Send only pending sales and for the same customer.
Check the result after the send (all / partial / none) to spot sales that were not updated.
Keep the "Pc Kasse" payment method properly configured.
Validate the flow with a sample sale before operating normally.