Skip to main content

Connecting Scaleway billing access

Factor Fifty collects Scaleway resource charges through the Billing FinOps API and compares them with monthly consumption for the connected Projects. The connection uses a dedicated billing application in the customer's existing Organization. This API path requires no customer export bucket or scheduled export.

Private preview

Your Factor Fifty platform administrator must arrange collector activation for the environment. Saving the connection verifies billing access; collection and successful import are separate steps. History is limited by the customer's retention plan and the data Scaleway makes available.

Understand the access scope​

Grant BillingReadOnly at Organization scope to a dedicated application such as FactorFifty-billing. This is an Organization-wide grant to billing information, including information beyond the Project selected in Factor Fifty. Project filters and an API key's preferred Project do not create a Project-only billing permission. Review Scaleway's permission sets and billing concepts.

Factor Fifty collects the selected Project's charges and consumption. It does not fetch the whole Organization's invoices for this connection. Other Projects and Organization-wide charges without a selected Project are outside its coverage. Several Project connections therefore do not automatically represent the complete Organization invoice.

Keep this application separate from the operational reader. The reader needs Organization-scoped ProjectReadOnly plus its product permissions. The billing application needs BillingReadOnly; the billing form uses an already connected Project, so it does not require Project discovery permissions on the billing key.

Before you begin​

You need:

  • A Project already connected to the correct customer through the operational reader.
  • Its Factor Fifty project UUID and Scaleway project ID.
  • A Scaleway operator authorized to create the application, policy and API key in that Organization.
  • A Factor Fifty platform administrator to complete billing onboarding.

The Factor Fifty project UUID identifies the project in Factor Fifty's project URL. The Scaleway project ID identifies the provider Project shown on its connection/environment. Do not substitute the Organization ID for either field.

Create the billing identity in Scaleway​

  1. Select the customer Organization in the Scaleway console.
  2. Under IAM & API keys, create an application named FactorFifty-billing.
  3. Create a policy whose principal is that application.
  4. Add an Organization-scoped rule granting BillingReadOnly.
  5. Create an API key with the application as bearer.
  6. Save its Access Key and Secret Key securely and record its expiry.

The setup operator needs IAM administration rights; the billing application does not need IAMManager, BillingManager, OrganizationManager or workload-management permissions. See Scaleway's application, policy and API-key instructions.

Connect billing in Factor Fifty​

  1. Open the customer and select Billing sources.
  2. Choose Scaleway billing.
  3. Enter a recognizable Display name.
  4. Enter the Factor Fifty project UUID and Scaleway project ID for the existing operational connection.
  5. Enter the dedicated Billing Access Key and Billing Secret Key.
  6. Select Connect billing.

Factor Fifty derives the Organization from the customer's existing connection, verifies the billing key against the provider API, and stores it encrypted. The reader key is not used as the billing key. Repeat for additional Projects with approved coverage; overlapping billing connections for the same Project are rejected.

Verify collection​

The billing source starts in PROVISIONING. Review its freshness/import information and consumption comparison after collection. ACTIVE confirms a usable source connection; it does not mean every historical month has imported or that an invoice has been reconciled.

The collector refreshes current and previous months while draining historical backfill. It retains raw evidence and publishes complete monthly snapshots after comparing daily-window totals with a month-wide pull. A failed or inconsistent fetch withholds that snapshot and preserves the previous imported data. The configured polling interval is not a promise of provider data freshness.

Financial dashboards use the PostgreSQL data source for Scaleway. They show raw usage costs, which can differ from invoice amounts. Amortized, contracted and list totals are unavailable, rather than zero. Billing tags and quantities are not supplied by the resource-charge schema; names and locality may also be missing. Charges are marked Unclassified because the feed does not identify usage versus commitment purchases, refunds or credits. Scaleway documents differences between raw FinOps charges and invoice/consumption data.

Rotate or disconnect billing​

To rotate, create a new billing application key and submit Scaleway billing again with the same Project identifiers and the replacement key. The existing billing connection is retained and its dedicated credential is updated after validation. Repeat for every billing connection that used the old key. Verify another collection before revoking the old key in Scaleway.

Use Disconnect on the billing source to remove it through Factor Fifty's disconnection flow. The dedicated stored billing credential is removed when cleanup completes; the operational reader remains separate. Revoke the application key in Scaleway if it is no longer used elsewhere. Never revoke a shared key before checking its other uses.

Troubleshooting​

SymptomCheck
Billing verification returns 403Organization-scoped BillingReadOnly, correct application bearer, key expiry and Organization
“Connection is outside this customer scope”The existing operational Project belongs to this customer and the identifiers match
Source stays PROVISIONINGAsk the platform administrator to verify collector activation and import health
Source is ACTIVE but the dashboard is emptyThe requested month/Project has charge data and a successful import; review freshness and backfill
Daily-window reconciliation failsAsk the administrator to inspect provider time-window behavior; no inconsistent snapshot is published
Consumption comparison reports a differenceCompare identical Project/month/currency scopes; raw-charge rounding and financial adjustments can differ

Use the Scaleway invoice as the authoritative payable document. Do not use a selected-Project raw-usage view as proof of the Organization's final bill.