name: rs-waybill description: Integrate with the Georgian Revenue Service (RS.GE) Electronic Waybill SOAP web service. Use this skill when working with waybill creation, activation, closing, querying, goods management, transporter operations, invoices, templates, bar codes, car numbers, and all RS.GE WayBillService API methods.

RS.GE Electronic Waybill Service Integration

Service Overview

This skill provides integration with the Georgian Revenue Service (RS.GE) Electronic Waybill (ელექტრონული ზედნადები) SOAP Web Service.

• WSDL/Endpoint: https://services.rs.ge/WayBillService/WayBillService.asmx
• Protocol: SOAP XML Web Service
• Authentication: Service user credentials (su, sp) passed with every method call

Test Credentials

Waybill Types

CRITICAL: Type-Specific Field Requirements

Type 1 - Internal Transfer (შიდა გადაზიდვა)

• BUYER_TIN must be empty
• Driver info required for transport types

Type 2 - Delivery (მიწოდება)

• START_ADDRESS: Required
• END_ADDRESS: Required
• DRIVER_TIN: Required (11 digits, or set CHEK_DRIVER_TIN=0 for foreigner)
• DRIVER_NAME: Required
• CAR_NUMBER: Required (format: AA123BB, no dashes!)
• TRANS_ID: 1 (automobile) or other valid transport type

Type 3 - Without Transport (ტრანსპორტირების გარეშე) ⚠️

CRITICAL: These fields MUST be EMPTY - otherwise RS.ge returns misleading errors!

• START_ADDRESS: "" (empty!)
• END_ADDRESS: "" (empty!)
• DRIVER_TIN: ""
• DRIVER_NAME: ""
• CAR_NUMBER: ""
• TRANS_ID: 0

WARNING: If addresses are provided for Type 3, RS.ge returns error -1036 "Invalid unit" which is completely misleading! The actual problem is the non-empty addresses.

Type 6 - Sub-waybill (ქვე-ზედნადები)

• PAR_ID: Required - must specify parent waybill ID

Valid Unit IDs

Note: Unit ID 6 does NOT exist!

Valid Transport Type IDs

Car Number Format

Georgian plates must be in format AA123BB (no dashes). Examples:

• Correct: AA123BB, TT999ZZ
• Wrong: AA-123-BB, aa123bb

Common Error Codes and Solutions

Waybill Statuses

Workflow

1. Create/Save waybill with save_waybill (status=0)
2. Activate with send_waybill or send_waybill_vd (status=1, gets unique number)
3. Close/Complete with close_waybill or close_waybill_vd (status=2)
4. Optionally cancel with ref_waybill or delete with del_waybill
5. Optionally create invoice with save_invoice

For transporter flow: seller sends to transporter -> transporter fills fields with save_waybill_transporter -> activates with send_waybill_transporter -> closes with close_waybill_transporter.

Implementation Guidelines

When implementing RS Waybill integration:

1. All methods require su and sp (service username and password) as the first two parameters.
2. XML format: The service uses XML nodes for complex data structures (waybills, goods lists, wood documents).
3. Date format: Use ISO format yyyy-MM-ddTHH:mm:ss (e.g., 2024-10-07T12:08:47).
4. Status filter format: Comma-delimited with leading/trailing commas for single status: ,1, for one status, ,1,2, for multiple.
5. Error handling: Check STATUS in response XML. Negative values indicate errors. Use get_error_codes to get error descriptions.
6. CATEGORY field: Empty or 0 = normal, 1 = wood/timber.
7. IS_MED field: Empty or 0 = normal, 1 = medication.
8. CHEK_BUYER_TIN / CHEK_DRIVER_TIN: 0 = foreigner, 1 = Georgian citizen.
9. TRAN_COST_PAYER: 1 = buyer pays, 2 = seller pays.
10. VAT_TYPE: 0 = normal, 1 = zero-rated, 2 = non-taxable.

For full API method signatures and XML structures, see the reference document: references/api-methods.md