JournalEntry Class
Properties Methods Events Config Settings Errors
A JournalEntry represents a general journal entry made directly in the company's chart of accounts.
Syntax
JournalEntry
Remarks
A JournalEntry represents a general journal entry made directly in the company's chart of accounts.
A journal entry must include one or more JournalLines. To set credit or debit lines, first set the appropriate value of LineCount. Then for each line, set an Account (Name or Id) and an Amount. You may set Entity to associate a customer or vendor with the line, and Class and Memo may be set as well.
Before adding the journal entry to QuickBooks, the transaction must be in balance: The total amount of the credit lines must be equal to the total amount of the debit lines. If the transaction is not in balance, QuickBooks will return an error.
If desired, you may set a RefNumber and TransactionDate for the journal entry as well.
Required Fields (Add):JournalLines
Supported Methods:Add, Get (Id), Cancel, Delete
Example
JournalEntry1.RefNumber = "123"
JournalEntry1.TransactionDate = "2013-12-16"
JournalEntry1.JournalLineCount = 2
JournalEntry1.JournalLineType(0) = jltCredit
JournalEntry1.JournalLineAccountName(0) = "Trucks:Depreciation" '*
JournalEntry1.JournalLineEntityName(0) = "Annual Depreciation" '*
JournalEntry1.JournalLineAmount(0) = "3000.00"
JournalEntry1.JournalLineType(1) = jltDebit
JournalEntry1.JournalLineAccountName(1) = "Depreciation Expense" '*
JournalEntry1.JournalLineAmount(1) = "3000.00"
JournalEntry1.Add()
'*: Item must already exist in QuickBooks.
The class supports a variety of other operations as well. The class's Get, Cancel, and Delete methods may be used to retrieve, cancel, and delete journal entries, respectively. The ObjSearch Class may be used to search for JournalEntry records in the QuickBooks database.
Property List
The following is the full list of the properties of the class with short descriptions. Click on the links for further details.
Adjustment | Indicates whether this Journal Entry is an adjustment or not. |
JournalLines | Specifies a collection of credit or debit transactions inside a General Journal Entry. |
QBConnectionString | An aggregate consisting of various QuickBooks connection properties. |
QBRequestAggregate | The request aggregate. |
QBRequestId | The Id of the next message to be sent to QuickBooks. |
QBRequestMode | Defines whether the request is made online or stored offline. |
QBResponseAggregate | The last QBXML response aggregate received from QuickBooks. |
QBXMLVersion | The version of QBXML used in the outgoing message. |
RefId | An alphanumerical identifier generated by the server. |
RefNumber | Reference number for the transaction. |
TransactionDate | Date of transaction. |
Method List
The following is the full list of the methods of the class with short descriptions. Click on the links for further details.
Add | Adds the record into QuickBooks. |
Cancel | Cancels (voids) the transaction. |
CheckRequestStatus | Checks whether or not the specified request was processed by QuickBooks. |
CloseQBConnection | Closes a persistent connection to QuickBooks. |
Config | Sets or retrieves a configuration setting. |
Delete | Deletes the record from QuickBooks. |
Get | Gets a single record from QuickBooks. |
GetCustomField | Gets a custom field value from QuickBooks. |
ImportQBXML | Imports a QBXML response aggregate. |
OpenQBConnection | Opens a persistent connection to QuickBooks. |
Reset | Resets all properties to their defaults. |
SetCustomField | Sets a custom field value within QuickBooks. |
Update | Updates the sales order in QuickBooks. |
Event List
The following is the full list of the events fired by the class with short descriptions. Click on the links for further details.
Error | Information about errors during data delivery. |
SSLServerAuthentication | Fired after the server presents its certificate to the client. |
SSLStatus | Fired when secure connection progress messages are available. |
Status | Shows the progress of the QuickBooks connection. |
Warning | Fired when a warning occurs. |
Config Settings
The following is a list of config settings for the class with short descriptions. Click on the links for further details.
AppendAfter | Appends an XML tag after the specified QBXML element. |
AuthFlags | Connection Flags (use for QuickBooks Simple Start). |
EditSequence | An identifier for this copy of the object. |
EnforceMaxLength | Indicates whether to enforce max lengths for QB Fields. |
GetHighestVersion | Highest QBXMLVersion supported by the installed instance of QuickBooks. |
GetRequestProcessorDLLVersion | Returns the version of the QB Request Processor that is installed on your system. |
GetSupportedVersions | Returns a list of QBXMLVersions that are supported by QuickBooks. |
IsReadOnly | This causes the QuickBooks authorization dialog to display text informing the user that its access will be read-only. |
PersonalDataPref | Whether the connecting application will require access to personal data such as SSN or credit card information. |
QBConnectionMode | The mode of connection to QuickBooks. |
QBFileStatus | The status of the company file as it pertains to accepting connections. |
QBOpenCompanyFile | The file currently open in QuickBooks. |
SendRawXML | Sends specified XML to quickbooks without modification. |
SSLAcceptServerCert | The SSL certificate being used by the QuickBooks Gateway (aka Remote Connector). |
SSLAcceptServerCertFile | The SSL certificate file being used by the QuickBooks Gateway (aka Remote Connector). |
StopOnError | Specifies how QuickBooks is to proceed if an error occurs in processing of the current request. |
TimeCreated | The time the object was created. |
TimeModified | The time the object was created. |
UnattendedModePref | Whether connecting while QuickBooks is closed is required or optional for the user. |
WarningCodes | A comma-separated list of QuickBooks warning codes that should not result in an exception. |
BuildInfo | Information about the product's build. |
CodePage | The system code page used for Unicode to Multibyte translations. |
LicenseInfo | Information about the current license. |
MaskSensitiveData | Whether sensitive data is masked in log messages. |
ProcessIdleEvents | Whether the class uses its internal event loop to process events when the main thread is idle. |
SelectWaitMillis | The length of time in milliseconds the class will wait when DoEvents is called if there are no events to process. |
UseInternalSecurityAPI | Whether or not to use the system security libraries or an internal implementation. |
Adjustment Property (JournalEntry Class)
Indicates whether this Journal Entry is an adjustment or not.
Syntax
ANSI (Cross Platform) int GetAdjustment();
int SetAdjustment(int iAdjustment); Unicode (Windows) INT GetAdjustment();
INT SetAdjustment(INT iAdjustment);
Possible Values
JEA_NOT_SET(0),
JEA_IS_ADJUSTMENT(1),
JEA_IS_NOT_ADJUSTMENT(2)
int inqb_journalentry_getadjustment(void* lpObj);
int inqb_journalentry_setadjustment(void* lpObj, int iAdjustment);
int GetAdjustment();
int SetAdjustment(int iAdjustment);
Default Value
0
Remarks
When a change is an "adjustment," the original information is retained, usually so an accountant can see the effects of the adjustment. The use of this property requires QBXMLVersion to be 3.0 or greater.
Data Type
Integer
JournalLines Property (JournalEntry Class)
Specifies a collection of credit or debit transactions inside a General Journal Entry.
Syntax
InQBList<InQBJournalLine>* GetJournalLines(); int SetJournalLines(InQBList<InQBJournalLine>* val);
int inqb_journalentry_getjournallinecount(void* lpObj);
int inqb_journalentry_setjournallinecount(void* lpObj, int iJournalLineCount);
char* inqb_journalentry_getjournallineaccountid(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallineaccountid(void* lpObj, int journallineindex, const char* lpszJournalLineAccountId);
char* inqb_journalentry_getjournallineaccountname(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallineaccountname(void* lpObj, int journallineindex, const char* lpszJournalLineAccountName);
char* inqb_journalentry_getjournallineamount(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallineamount(void* lpObj, int journallineindex, const char* lpszJournalLineAmount);
int inqb_journalentry_getjournallinebillablestatus(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallinebillablestatus(void* lpObj, int journallineindex, int iJournalLineBillableStatus);
char* inqb_journalentry_getjournallineclassid(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallineclassid(void* lpObj, int journallineindex, const char* lpszJournalLineClassId);
char* inqb_journalentry_getjournallineclassname(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallineclassname(void* lpObj, int journallineindex, const char* lpszJournalLineClassName);
char* inqb_journalentry_getjournallineentityid(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallineentityid(void* lpObj, int journallineindex, const char* lpszJournalLineEntityId);
char* inqb_journalentry_getjournallineentityname(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallineentityname(void* lpObj, int journallineindex, const char* lpszJournalLineEntityName);
char* inqb_journalentry_getjournallinelineid(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallinelineid(void* lpObj, int journallineindex, const char* lpszJournalLineLineId);
int inqb_journalentry_getjournallinetype(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallinetype(void* lpObj, int journallineindex, int iJournalLineType);
char* inqb_journalentry_getjournallinememo(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallinememo(void* lpObj, int journallineindex, const char* lpszJournalLineMemo);
char* inqb_journalentry_getjournallinetaxitemid(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallinetaxitemid(void* lpObj, int journallineindex, const char* lpszJournalLineTaxItemId);
char* inqb_journalentry_getjournallinetaxitemname(void* lpObj, int journallineindex);
int inqb_journalentry_setjournallinetaxitemname(void* lpObj, int journallineindex, const char* lpszJournalLineTaxItemName);
int GetJournalLineCount();
int SetJournalLineCount(int iJournalLineCount); QString GetJournalLineAccountId(int iJournalLineIndex);
int SetJournalLineAccountId(int iJournalLineIndex, QString qsJournalLineAccountId); QString GetJournalLineAccountName(int iJournalLineIndex);
int SetJournalLineAccountName(int iJournalLineIndex, QString qsJournalLineAccountName); QString GetJournalLineAmount(int iJournalLineIndex);
int SetJournalLineAmount(int iJournalLineIndex, QString qsJournalLineAmount); int GetJournalLineBillableStatus(int iJournalLineIndex);
int SetJournalLineBillableStatus(int iJournalLineIndex, int iJournalLineBillableStatus); QString GetJournalLineClassId(int iJournalLineIndex);
int SetJournalLineClassId(int iJournalLineIndex, QString qsJournalLineClassId); QString GetJournalLineClassName(int iJournalLineIndex);
int SetJournalLineClassName(int iJournalLineIndex, QString qsJournalLineClassName); QString GetJournalLineEntityId(int iJournalLineIndex);
int SetJournalLineEntityId(int iJournalLineIndex, QString qsJournalLineEntityId); QString GetJournalLineEntityName(int iJournalLineIndex);
int SetJournalLineEntityName(int iJournalLineIndex, QString qsJournalLineEntityName); QString GetJournalLineLineId(int iJournalLineIndex);
int SetJournalLineLineId(int iJournalLineIndex, QString qsJournalLineLineId); int GetJournalLineType(int iJournalLineIndex);
int SetJournalLineType(int iJournalLineIndex, int iJournalLineType); QString GetJournalLineMemo(int iJournalLineIndex);
int SetJournalLineMemo(int iJournalLineIndex, QString qsJournalLineMemo); QString GetJournalLineTaxItemId(int iJournalLineIndex);
int SetJournalLineTaxItemId(int iJournalLineIndex, QString qsJournalLineTaxItemId); QString GetJournalLineTaxItemName(int iJournalLineIndex);
int SetJournalLineTaxItemName(int iJournalLineIndex, QString qsJournalLineTaxItemName);
Remarks
JournalLines represents a collection of Debit and Credit lines. All Debit and Credit lines must be in balance. The total Amount for all Debit lines must match the total Amount for all Debit lines, or QuickBooks will return an error.
Note: If no amount is included in the first credit or debit line of a journal entry in the QuickBooks user interface, then subsequent SDK queries on that JournalEntry object will fail XML validation.
This property is not available at design time.
Data Type
QBConnectionString Property (JournalEntry Class)
An aggregate consisting of various QuickBooks connection properties.
Syntax
ANSI (Cross Platform) char* GetQBConnectionString();
int SetQBConnectionString(const char* lpszQBConnectionString); Unicode (Windows) LPWSTR GetQBConnectionString();
INT SetQBConnectionString(LPCWSTR lpszQBConnectionString);
char* inqb_journalentry_getqbconnectionstring(void* lpObj);
int inqb_journalentry_setqbconnectionstring(void* lpObj, const char* lpszQBConnectionString);
QString GetQBConnectionString();
int SetQBConnectionString(QString qsQBConnectionString);
Default Value
""
Remarks
QBConnectionString allows the user to customize the application's interaction with QuickBooks.
The connection properties should be formatted in a sequence as follows:
propertyname = "propertyvalue" propertyname = "propertyvalue" ...
The order is irrelevant, and the whitespace around the equal sign is optional.
The following properties are currently supported:
ApplicationName | The name of the developer's application. This name will appear when the application first connects to QuickBooks; QuickBooks will display this name and prompt the user to grant or refuse access. |
CompanyFile | The name of the company file to open. If QuickBooks is not currently open with a company
file, QuickBooks will be automatically opened in the background with the file specified.
Do not set CompanyFile when QuickBooks is open; if QuickBooks is open through the
application UI, only that company file may be used.
This setting is not applicable when communicating with QB Connector. |
URL | The URL for the Remote Connector, e.g., 'http://localhost:2080'. If the URL is specified, the class will not communicate directly with QuickBooks, and will instead send a request to the specified web address. QuickBooks and the Remote Connector should be installed at the remote location, and if the connector is listening on the specified port, it will communicate the class's request to QuickBooks, and return the response. |
User | A username for the Remote Connector connection (if required on the Connector side) |
Password | A password for the Remote Connector connection (if required on the Connector side) |
Timeout | A timeout, in seconds, for the Remote Connector connection. If the Connector does not finish and respond within the chosen length of time, the class will generate an exception instead of hanging. |
DelayAfterClose | A delay, in milliseconds, to be applied after each time a connection to QuickBooks is closed. If QuickBooks is generating internal errors (in particular with automatic login) setting this delay to a positive value may solve the problem. |
FirewallHost | Contains the name or IP address of firewall. If a FirewallHost is given, the requested connections will be authenticated through the specified firewall when connecting. |
FirewallPassword | Contains a password if authentication is to be used when connecting through the firewall. If FirewallHost is specified, the FirewallUser and FirewallPassword configs are used to connect and authenticate to the given firewall. If the authentication fails, the class fails with an error. |
FirewallPort | Contains the TCP port for the firewall FirewallHost. Note this is set automatically when FirewallType is set to a valid value. |
FirewallType | Determines the type of firewall to connect through. Supported values are: 0 - no firewall (default), 1 - Tunneling proxy, 2 - SOCKS4 proxy, and 3 - SOCKS5 proxy. For the Tunneling proxy (1), the FirewallPort defaults to 80. For SOCKS4 (2) and SOCKS5 (3) the FirewallPort defaults to 1080. |
FirewallUser | Contains a user name if authentication is to be used connecting through a firewall. If the FirewallHost is specified, the FirewallUser and FirewallPassword configs are used to connect and authenticate to the given firewall. If the authentication fails, the class fails with an error. |
ProxyAuthorization | Supported values are 0 - Basic authorization, 1 - Digest authentication, 3 - No authentication, and 4 - NTLM authentication. |
ProxyPassword | Contains a password if authentication is to be used for the proxy. |
ProxyPort | Contains the TCP port for a ProxyServer; (default 80). |
ProxySSL | Determines when to use SSL for the connection to the proxy. The applicable values are 0 - Automatic (SSL for https URLs, non-SSL for http URLs), 1 - The connection is always SSL-enabled, 2 - SSL is not enabled for any connection, and 3 - Connection is through a tunneling proxy. |
ProxyServer | If a ProxyServer is specified, then the HTTP request is sent to the proxy instead of the server otherwise specified. If the ProxyServer is set to a Domain Name, a DNS request is initiated and upon successful termination of the request, the ProxyServer is set to the corresponding address. If the search is not successful, an error is returned. |
ProxyUser | Contains a user name, if authentication is to be used for the proxy. |
LocalHost | The name of the local host or user-assigned IP interface through which connections are initiated or accepted. |
LocalPort | The TCP port in the local host where the class binds. |
UseRDS | Whether to connect using Remote Data Sharing (RDS). If set to True, the class will attempt to connect using the RDS client installed on the machine. The RDS client and server must be configured separately. The default value is False. |
Data Type
String
QBRequestAggregate Property (JournalEntry Class)
The request aggregate.
Syntax
ANSI (Cross Platform) char* GetQBRequestAggregate();
int SetQBRequestAggregate(const char* lpszQBRequestAggregate); Unicode (Windows) LPWSTR GetQBRequestAggregate();
INT SetQBRequestAggregate(LPCWSTR lpszQBRequestAggregate);
char* inqb_journalentry_getqbrequestaggregate(void* lpObj);
int inqb_journalentry_setqbrequestaggregate(void* lpObj, const char* lpszQBRequestAggregate);
QString GetQBRequestAggregate();
int SetQBRequestAggregate(QString qsQBRequestAggregate);
Default Value
""
Remarks
This property will be populated when QBRequestMode is set to rmOffline and a method is called. This is used when working with the QBWCServer class to generate requests to be sent to QuickBooks Web Connector.
This property is not available at design time.
Data Type
String
QBRequestId Property (JournalEntry Class)
The Id of the next message to be sent to QuickBooks.
Syntax
ANSI (Cross Platform) char* GetQBRequestId();
int SetQBRequestId(const char* lpszQBRequestId); Unicode (Windows) LPWSTR GetQBRequestId();
INT SetQBRequestId(LPCWSTR lpszQBRequestId);
char* inqb_journalentry_getqbrequestid(void* lpObj);
int inqb_journalentry_setqbrequestid(void* lpObj, const char* lpszQBRequestId);
QString GetQBRequestId();
int SetQBRequestId(QString qsQBRequestId);
Default Value
""
Remarks
The next message Id to be sent to QuickBooks. Message Id's are used by CheckRequestStatus to check on the status of previously made requests.
This property allows the user to determine whether a previous request was successfully processed by QuickBooks. Ordinarily QuickBooks either processes requests successfully or returns an error, but in the event of a power outage or other system failure, QuickBooks might or might not have time to process a request before issuing a response.
QuickBooks stores internally a list of QBRequestIds for which it has processed a request, and updated its internal state accordingly. Use of this property in conjunction with CheckRequestStatus allows the user to query this internal list.
To enable error recovery, the user application should store the value of QBRequestId before submitting a request to QuickBooks. If a system failure occurs, CheckRequestStatus should be called with this value of QBRequestId to find whether the request was processed before the system failed.
Unique values for QBRequestId will be generated on startup and after each request to QuickBooks. The automatically generated value may be overwritten by the user. Error checking may be turned off by setting QBRequestId equal to the empty string. See CheckRequestStatus for more information on error recovery.
This property is not available at design time.
Data Type
String
QBRequestMode Property (JournalEntry Class)
Defines whether the request is made online or stored offline.
Syntax
ANSI (Cross Platform) int GetQBRequestMode();
int SetQBRequestMode(int iQBRequestMode); Unicode (Windows) INT GetQBRequestMode();
INT SetQBRequestMode(INT iQBRequestMode);
Possible Values
RM_ONLINE(0),
RM_OFFLINE(1)
int inqb_journalentry_getqbrequestmode(void* lpObj);
int inqb_journalentry_setqbrequestmode(void* lpObj, int iQBRequestMode);
int GetQBRequestMode();
int SetQBRequestMode(int iQBRequestMode);
Default Value
0
Remarks
This property defines the behavior of the class when calling a method. Possible values are:
0 (rmOnline - default) | The request is made normally. |
1 (rmOffline) | The request is generated but not sent, and QBRequestAggregate is populated. |
For normal communication to QuickBooks either directly or through the QBConnector application use the default online mode.
Data Type
Integer
QBResponseAggregate Property (JournalEntry Class)
The last QBXML response aggregate received from QuickBooks.
Syntax
ANSI (Cross Platform) char* GetQBResponseAggregate();
int SetQBResponseAggregate(const char* lpszQBResponseAggregate); Unicode (Windows) LPWSTR GetQBResponseAggregate();
INT SetQBResponseAggregate(LPCWSTR lpszQBResponseAggregate);
char* inqb_journalentry_getqbresponseaggregate(void* lpObj);
int inqb_journalentry_setqbresponseaggregate(void* lpObj, const char* lpszQBResponseAggregate);
QString GetQBResponseAggregate();
int SetQBResponseAggregate(QString qsQBResponseAggregate);
Default Value
""
Remarks
The last QBXML response aggregate received from QuickBooks. This property is set whenever a response is received from QuickBooks.
This property may also be set to a response aggregate. When set to a QBXML aggregate, such as a response from ObjSearch or QBWCServer the class will parse the response as if it had been received directly from QuickBooks and the applicable properties will be updated.
This property is not available at design time.
Data Type
String
QBXMLVersion Property (JournalEntry Class)
The version of QBXML used in the outgoing message.
Syntax
ANSI (Cross Platform) char* GetQBXMLVersion();
int SetQBXMLVersion(const char* lpszQBXMLVersion); Unicode (Windows) LPWSTR GetQBXMLVersion();
INT SetQBXMLVersion(LPCWSTR lpszQBXMLVersion);
char* inqb_journalentry_getqbxmlversion(void* lpObj);
int inqb_journalentry_setqbxmlversion(void* lpObj, const char* lpszQBXMLVersion);
QString GetQBXMLVersion();
int SetQBXMLVersion(QString qsQBXMLVersion);
Default Value
"3.0"
Remarks
The version of QBXML used in the outgoing message. Except as noted in the documentation, a value of "1.1" will suffice for all requests, and for all versions of QuickBooks which support integrated applications.
With each release of QuickBooks since 2002, a corresponding version of the QuickBooks SDK has also been released: 1.0 for QuickBooks 2002, 2.0 for QuickBooks 2003, 3.0 for QuickBooks 2004, etc., up to 8.0 for QuickBooks 2009. In addition, each release of QuickBooks continues to support all earlier versions of the SDK, meaning that requests using version 1.1 of the QuickBooks SDK are supported by all versions of QuickBooks. However, new requests and newer fields in existing requests are only supported in later versions of the QuickBooks SDK. As such, it is recommended that you set the QBXMLVersion property to correspond to the version of QuickBooks you are interacting with. These values are:
QuickBooks 2002 | 1.0, 1.1 |
QuickBooks 2003 | 2.0 |
QuickBooks 2004 | 3.0 |
QuickBooks 2005 | 4.0, 4.1 |
QuickBooks 2006 | 5.0 |
QuickBooks 2007 | 6.0 |
QuickBooks 2008 | 7.0 |
QuickBooks 2009 | 8.0 |
QuickBooks 2010 | 9.0 |
QuickBooks 2011 | 10.0 |
QuickBooks 2012 | 11.0 |
QuickBooks 2013 | 12.0 |
QuickBooks 2014 | 13.0 |
QuickBooks 2015 | 14.0 |
QuickBooks 2016 | 15.0 |
QuickBooks Canadian 2003 | CA2.0 |
QuickBooks Canadian 2004 to 2007 | CA3.0 |
QuickBooks UK 2003 | UK2.0 |
QuickBooks UK 2004 to 2007 | UK3.0 |
QuickBooks Australian 2003 | OZ2.0 |
QuickBooks Australian 2004 to 2007 | AU3.0 |
This property is not available at design time.
Data Type
String
RefId Property (JournalEntry Class)
An alphanumerical identifier generated by the server.
Syntax
ANSI (Cross Platform) char* GetRefId(); Unicode (Windows) LPWSTR GetRefId();
char* inqb_journalentry_getrefid(void* lpObj);
QString GetRefId();
Default Value
""
Remarks
An Id is an alphanumerical identifier assigned by the server whenever an object is added to QuickBooks. It is guaranteed to be unique across all objects of the same type.
This property is read-only and not available at design time.
Data Type
String
RefNumber Property (JournalEntry Class)
Reference number for the transaction.
Syntax
ANSI (Cross Platform) char* GetRefNumber();
int SetRefNumber(const char* lpszRefNumber); Unicode (Windows) LPWSTR GetRefNumber();
INT SetRefNumber(LPCWSTR lpszRefNumber);
char* inqb_journalentry_getrefnumber(void* lpObj);
int inqb_journalentry_setrefnumber(void* lpObj, const char* lpszRefNumber);
QString GetRefNumber();
int SetRefNumber(QString qsRefNumber);
Default Value
""
Remarks
This is the reference number assigned to a transaction. Depending on the type of transaction, it appears in the QuickBooks user interface as Bill Number, Invoice Number, etc.
Reference numbers are alphanumeric strings and are not limited to actually being numbers.
For some types of transactions, if RefNumber is not assigned, QuickBooks will automatically assign a unique one. Reference numbers should generally be unique, but are not guaranteed to be so. It is recommended that applications generating their own reference numbers take steps to ensure their uniqueness.
Data Type
String
TransactionDate Property (JournalEntry Class)
Date of transaction.
Syntax
ANSI (Cross Platform) char* GetTransactionDate();
int SetTransactionDate(const char* lpszTransactionDate); Unicode (Windows) LPWSTR GetTransactionDate();
INT SetTransactionDate(LPCWSTR lpszTransactionDate);
char* inqb_journalentry_gettransactiondate(void* lpObj);
int inqb_journalentry_settransactiondate(void* lpObj, const char* lpszTransactionDate);
QString GetTransactionDate();
int SetTransactionDate(QString qsTransactionDate);
Default Value
""
Remarks
The date of the transaction.
The standard formatting for dates is YYYY-MM-DD; i.e., September 2, 2002 is formatted as 2002-09-02. When getting the value of a date property, the date will always be in this format.
When setting the value of a date property, the formats MM-DD-YY, MM-DD-YYYY, MM/DD/YY, and MM/DD/YYYY are also acceptable. Dates in these formats will be automatically parsed and stored in YYYY-MM-DD format.
This property is required unless QBXMLVersion is at least "2.0" (in which case QuickBooks will assign a default).
Data Type
String
Add Method (JournalEntry Class)
Adds the record into QuickBooks.
Syntax
ANSI (Cross Platform) int Add(); Unicode (Windows) INT Add();
int inqb_journalentry_add(void* lpObj);
int Add();
Remarks
Add is used to add the object to QuickBooks.
If QuickBooks is able to add the object, it will return a copy of the object, and the values of all properties will be reset from the QuickBooks response. The QBResponseAggregate property will also be set to the entire QBXML aggregate received from QuickBooks.
For example, read-only properties such as RefIds will be assigned. In transaction objects, line item information will be filled out, and ItemGroups will be broken up into their respective Items. Also, a total will be calculated.
If QuickBooks is not able to add the object, a trappable error will occur.
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
Cancel Method (JournalEntry Class)
Cancels (voids) the transaction.
Syntax
ANSI (Cross Platform) int Cancel(); Unicode (Windows) INT Cancel();
int inqb_journalentry_cancel(void* lpObj);
int Cancel();
Remarks
Cancel causes the transaction to be voided in QuickBooks. The amount of the transaction and all line item quantities are changed to zero, and the memo is changed to "VOID:". The transaction will not, however, be deleted.
The transaction canceled in QuickBooks is the one specified by RefId. If the value of RefId is known then Get should first be called to retrieve the transaction. Otherwise the ObjSearch class should be used to search for the desired transaction in the QuickBooks database.
As the QuickBooks response to Cancel does not include the updated transaction, the values of all properties are instead set to their defaults. To get a copy of the updated transaction, the value of RefId should first be stored, and then Get should be called.
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
CheckRequestStatus Method (JournalEntry Class)
Checks whether or not the specified request was processed by QuickBooks.
Syntax
ANSI (Cross Platform) char* CheckRequestStatus(const char* lpszRequestId); Unicode (Windows) LPWSTR CheckRequestStatus(LPCWSTR lpszRequestId);
char* inqb_journalentry_checkrequeststatus(void* lpObj, const char* lpszRequestId);
QString CheckRequestStatus(const QString& qsRequestId);
Remarks
This method allows the user to determine whether a previous request was successfully processed by QuickBooks. Ordinarily QuickBooks either processes requests successfully or returns an error, but in the event of a power outage or other system failure, QuickBooks might or might not have time to process a request before issuing a response.
QuickBooks stores internally a list of QBRequestIds for which it has processed a request, and updated its internal state accordingly. Use of this method allows the user to query the list for any RequestId whose value is known.
The method returns a string corresponding to the result of the query. If the request was processed successfully, an empty string ("") will be returned. If the request was not processed, the string "Request not processed." will be returned. If the request was processed but an error occurred, a string containing the error code and a description will be returned; for example, "801: A QuickBooks internal error has occurred."
See QBRequestId for more information on error recovery.
Error Handling (C++)
This method returns a String value; after it returns, call the GetLastErrorCode() method to obtain its result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message.
CloseQBConnection Method (JournalEntry Class)
Closes a persistent connection to QuickBooks.
Syntax
ANSI (Cross Platform) int CloseQBConnection(); Unicode (Windows) INT CloseQBConnection();
int inqb_journalentry_closeqbconnection(void* lpObj);
int CloseQBConnection();
Remarks
Invoking CloseQBConnection closes the QuickBooks connection specified in QBConnectionString. After the connection has been closed, the class will revert to its default behavior, and a new connection will be established for each request until QBConnectionString is invoked again.
In case the connection is already closed invoking CloseQBConnection will have no effect. Moreover, if multiple connections are open CloseQBConnection will only close the connection specified in QBConnectionString.
Be sure to always invoke this method after calling OpenQBConnection.
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
Config Method (JournalEntry Class)
Sets or retrieves a configuration setting.
Syntax
ANSI (Cross Platform) char* Config(const char* lpszConfigurationString); Unicode (Windows) LPWSTR Config(LPCWSTR lpszConfigurationString);
char* inqb_journalentry_config(void* lpObj, const char* lpszConfigurationString);
QString Config(const QString& qsConfigurationString);
Remarks
Config is a generic method available in every class. It is used to set and retrieve configuration settings for the class.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.
To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).
To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.
Error Handling (C++)
This method returns a String value; after it returns, call the GetLastErrorCode() method to obtain its result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message.
Delete Method (JournalEntry Class)
Deletes the record from QuickBooks.
Syntax
ANSI (Cross Platform) int Delete(); Unicode (Windows) INT Delete();
int inqb_journalentry_delete(void* lpObj);
int Delete();
Remarks
Delete causes the object to be deleted in QuickBooks. After this method is called, the values of all fields will be reset to their defaults.
The object deleted in QuickBooks is the one specified by RefId. This read-only property may be assigned either by calling Get or by assigning the value of QBResponseAggregate.
A typical example:
Customer.GetByName("John Smith") 'this will assign the RefId
Customer.Delete()
Deleting entity objects (Customer, Employee, and Vendor) requires that
QuickBooks be open in single-user mode. Transaction objects, however, may be deleted
while QuickBooks is in any mode.
Use this method with caution, as there is no way to recover deleted objects.
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
Get Method (JournalEntry Class)
Gets a single record from QuickBooks.
Syntax
ANSI (Cross Platform) int Get(const char* lpszId); Unicode (Windows) INT Get(LPCWSTR lpszId);
int inqb_journalentry_get(void* lpObj, const char* lpszId);
int Get(const QString& qsId);
Remarks
Get may be used to retrieve a single object from QuickBooks, based on its RefId. When the method is called, a search will be initiated for the requested object. If it is found, all properties of the class will be set to the information retrieved from QuickBooks. The QBResponseAggregate property will also be set to the entire QBXML aggregate received from QuickBooks.
The RefId of any class, or the Id of any reference property, may be used for the parameter. So for example, the following pseudocode would get customer information for a Customer listed on an Invoice:
Customer.Get( Invoice.CustomerId )
The GetByName method, present only in entity objects (Customer, Vendor, and Employee) and QBObject, may be used to get an object based on its Name. To retrieve multiple objects, to retrieve transaction objects whose RefId is not known, or to perform more advanced searches the ObjSearch class may be used.
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
GetCustomField Method (JournalEntry Class)
Gets a custom field value from QuickBooks.
Syntax
ANSI (Cross Platform) char* GetCustomField(const char* lpszFieldName); Unicode (Windows) LPWSTR GetCustomField(LPCWSTR lpszFieldName);
char* inqb_journalentry_getcustomfield(void* lpObj, const char* lpszFieldName);
QString GetCustomField(const QString& qsFieldName);
Remarks
This method will get the value of a custom field, which has been defined by the user from within the QuickBooks UI.
To read the values of custom fields, be sure to set QBXMLVersion to at least "2.0" when retrieving data from QuickBooks. Then, QuickBooks will return custom field information, and it will be accessible through this method.
You may also invoke Config to read the value of custom fields. However, to set the value of custom fields you must set QBXMLVersion to at least "3.0" and invoke SetCustomField.
Error Handling (C++)
This method returns a String value; after it returns, call the GetLastErrorCode() method to obtain its result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message.
ImportQBXML Method (JournalEntry Class)
Imports a QBXML response aggregate.
Syntax
ANSI (Cross Platform) int ImportQBXML(const char* lpszXMLData); Unicode (Windows) INT ImportQBXML(LPCWSTR lpszXMLData);
int inqb_journalentry_importqbxml(void* lpObj, const char* lpszXMLData);
int ImportQBXML(const QString& qsXMLData);
Remarks
This method imports a QBXML response aggregate. When called with a QBXML aggregate, such as a response from ObjSearch or QBWCServer the class will parse the response as if it had been received directly from QuickBooks and the applicable properties will be updated.
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
OpenQBConnection Method (JournalEntry Class)
Opens a persistent connection to QuickBooks.
Syntax
ANSI (Cross Platform) int OpenQBConnection(); Unicode (Windows) INT OpenQBConnection();
int inqb_journalentry_openqbconnection(void* lpObj);
int OpenQBConnection();
Remarks
Invoking OpenQBConnection will open a persistent connection to QuickBooks. After invoking OpenQBConnection, all requests such as Get, Add, etc. will use the established connection until CloseQBConnection is invoked.
The effect of OpenQBConnection is to increase performance. If OpenQBConnection is not invoked, a connection to QuickBooks will automatically be created and destroyed each time the class communicates with QuickBooks. Using OpenQBConnection will be faster, particularly in the case of automatic login.
After OpenQBConnection is invoked, QuickBooks will issue a connection ticket, and it will be stored in QBConnectionString. When CloseQBConnection is invoked the ticket will be invalidated, and any further attempts to use it will fail.
Be sure to invoke CloseQBConnection when you have finished communicating with QuickBooks. Leaving an open QuickBooks connection may lock out other integrated applications, affect QuickBooks performance, or cause other problems.
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
Reset Method (JournalEntry Class)
Resets all properties to their defaults.
Syntax
ANSI (Cross Platform) int Reset(); Unicode (Windows) INT Reset();
int inqb_journalentry_reset(void* lpObj);
int Reset();
Remarks
This method resets the values of all properties (and all special fields) to their defaults.
After calling this method, the class may be reused as if it were newly created.
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
SetCustomField Method (JournalEntry Class)
Sets a custom field value within QuickBooks.
Syntax
ANSI (Cross Platform) int SetCustomField(const char* lpszFieldName, const char* lpszFieldValue); Unicode (Windows) INT SetCustomField(LPCWSTR lpszFieldName, LPCWSTR lpszFieldValue);
int inqb_journalentry_setcustomfield(void* lpObj, const char* lpszFieldName, const char* lpszFieldValue);
int SetCustomField(const QString& qsFieldName, const QString& qsFieldValue);
Remarks
This method requires QuickBooks 2004 or above, with QBXMLVersion set to at least "3.0".
This method will immediately set the value of a QuickBooks custom field, which has been defined by the user from within the QuickBooks UI. Before calling this method, the preceding operation must retrieve the object from QuickBooks, using Get, ObjSearch, etc. Then, you may use SetCustomField to set custom field values (the fields will be modified or added, as appropriate).
Note that invoking this method will create a connection to QuickBooks if one is not already in place.
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
Update Method (JournalEntry Class)
Updates the sales order in QuickBooks.
Syntax
ANSI (Cross Platform) int Update(); Unicode (Windows) INT Update();
int inqb_journalentry_update(void* lpObj);
int Update();
Remarks
This method will update the sales order in QuickBooks.
When the method is called, an Update request will be submitted to QuickBooks. The sales order will have its information updated based on the various property values.
If QuickBooks is able to update the object, it will return a copy of the object, and the values of all properties will be reset from the QuickBooks response. The QBResponseAggregate property will also be set to the entire QBXML aggregate received from QuickBooks.
QBXMLVersion must be set to "3.0" or greater to update a sales order. Moreover, QBXMLVersion should be set to the same value when retrieving the sales order from QuickBooks (either through ObjSearch or through the Get method).
Error Handling (C++)
This method returns a result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. If an error occurs, the GetLastError() method can be called to retrieve the associated error message. (Note: This method's result code can also be obtained by calling the GetLastErrorCode() method after it returns.)
Error Event (JournalEntry Class)
Information about errors during data delivery.
Syntax
ANSI (Cross Platform) virtual int FireError(JournalEntryErrorEventParams *e);
typedef struct {
int ErrorCode;
const char *Description; int reserved; } JournalEntryErrorEventParams;
Unicode (Windows) virtual INT FireError(JournalEntryErrorEventParams *e);
typedef struct {
INT ErrorCode;
LPCWSTR Description; INT reserved; } JournalEntryErrorEventParams;
#define EID_JOURNALENTRY_ERROR 1 virtual INT INQB_CALL FireError(INT &iErrorCode, LPSTR &lpszDescription);
class JournalEntryErrorEventParams { public: int ErrorCode(); const QString &Description(); int EventRetVal(); void SetEventRetVal(int iRetVal); };
// To handle, connect one or more slots to this signal. void Error(JournalEntryErrorEventParams *e);
// Or, subclass JournalEntry and override this emitter function. virtual int FireError(JournalEntryErrorEventParams *e) {...}
Remarks
The Error event is fired in case of exceptional conditions during message processing.
ErrorCode contains an error code and Description contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.
SSLServerAuthentication Event (JournalEntry Class)
Fired after the server presents its certificate to the client.
Syntax
ANSI (Cross Platform) virtual int FireSSLServerAuthentication(JournalEntrySSLServerAuthenticationEventParams *e);
typedef struct {
const char *CertEncoded; int lenCertEncoded;
const char *CertSubject;
const char *CertIssuer;
const char *Status;
int Accept; int reserved; } JournalEntrySSLServerAuthenticationEventParams;
Unicode (Windows) virtual INT FireSSLServerAuthentication(JournalEntrySSLServerAuthenticationEventParams *e);
typedef struct {
LPCSTR CertEncoded; INT lenCertEncoded;
LPCWSTR CertSubject;
LPCWSTR CertIssuer;
LPCWSTR Status;
BOOL Accept; INT reserved; } JournalEntrySSLServerAuthenticationEventParams;
#define EID_JOURNALENTRY_SSLSERVERAUTHENTICATION 2 virtual INT INQB_CALL FireSSLServerAuthentication(LPSTR &lpCertEncoded, INT &lenCertEncoded, LPSTR &lpszCertSubject, LPSTR &lpszCertIssuer, LPSTR &lpszStatus, BOOL &bAccept);
class JournalEntrySSLServerAuthenticationEventParams { public: const QByteArray &CertEncoded(); const QString &CertSubject(); const QString &CertIssuer(); const QString &Status(); bool Accept(); void SetAccept(bool bAccept); int EventRetVal(); void SetEventRetVal(int iRetVal); };
// To handle, connect one or more slots to this signal. void SSLServerAuthentication(JournalEntrySSLServerAuthenticationEventParams *e);
// Or, subclass JournalEntry and override this emitter function. virtual int FireSSLServerAuthentication(JournalEntrySSLServerAuthenticationEventParams *e) {...}
Remarks
During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.
When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.
SSLStatus Event (JournalEntry Class)
Fired when secure connection progress messages are available.
Syntax
ANSI (Cross Platform) virtual int FireSSLStatus(JournalEntrySSLStatusEventParams *e);
typedef struct {
const char *Message; int reserved; } JournalEntrySSLStatusEventParams;
Unicode (Windows) virtual INT FireSSLStatus(JournalEntrySSLStatusEventParams *e);
typedef struct {
LPCWSTR Message; INT reserved; } JournalEntrySSLStatusEventParams;
#define EID_JOURNALENTRY_SSLSTATUS 3 virtual INT INQB_CALL FireSSLStatus(LPSTR &lpszMessage);
class JournalEntrySSLStatusEventParams { public: const QString &Message(); int EventRetVal(); void SetEventRetVal(int iRetVal); };
// To handle, connect one or more slots to this signal. void SSLStatus(JournalEntrySSLStatusEventParams *e);
// Or, subclass JournalEntry and override this emitter function. virtual int FireSSLStatus(JournalEntrySSLStatusEventParams *e) {...}
Remarks
The event is fired for informational and logging purposes only. This event tracks the progress of the connection.
Status Event (JournalEntry Class)
Shows the progress of the QuickBooks connection.
Syntax
ANSI (Cross Platform) virtual int FireStatus(JournalEntryStatusEventParams *e);
typedef struct {
const char *Message; int reserved; } JournalEntryStatusEventParams;
Unicode (Windows) virtual INT FireStatus(JournalEntryStatusEventParams *e);
typedef struct {
LPCWSTR Message; INT reserved; } JournalEntryStatusEventParams;
#define EID_JOURNALENTRY_STATUS 4 virtual INT INQB_CALL FireStatus(LPSTR &lpszMessage);
class JournalEntryStatusEventParams { public: const QString &Message(); int EventRetVal(); void SetEventRetVal(int iRetVal); };
// To handle, connect one or more slots to this signal. void Status(JournalEntryStatusEventParams *e);
// Or, subclass JournalEntry and override this emitter function. virtual int FireStatus(JournalEntryStatusEventParams *e) {...}
Remarks
The event is fired for informational and logging purposes only. Used to track the progress of the connection.
Warning Event (JournalEntry Class)
Fired when a warning occurs.
Syntax
ANSI (Cross Platform) virtual int FireWarning(JournalEntryWarningEventParams *e);
typedef struct {
int Code;
const char *Description; int reserved; } JournalEntryWarningEventParams;
Unicode (Windows) virtual INT FireWarning(JournalEntryWarningEventParams *e);
typedef struct {
INT Code;
LPCWSTR Description; INT reserved; } JournalEntryWarningEventParams;
#define EID_JOURNALENTRY_WARNING 5 virtual INT INQB_CALL FireWarning(INT &iCode, LPSTR &lpszDescription);
class JournalEntryWarningEventParams { public: int Code(); const QString &Description(); int EventRetVal(); void SetEventRetVal(int iRetVal); };
// To handle, connect one or more slots to this signal. void Warning(JournalEntryWarningEventParams *e);
// Or, subclass JournalEntry and override this emitter function. virtual int FireWarning(JournalEntryWarningEventParams *e) {...}
Remarks
The Warning event is fired when the class has produced, or will produce, possibly unexpected results.
Warnings may be generated by QuickBooks or the class. Starred warning codes correspond to warnings and warning codes generated by QuickBooks.
510* | Object added successfully, but cannot now be read. |
520* | Insufficient permissions to get all data. |
801 | Unable to update field (name). |
802 | Unable to parse name. |
Warning 801 will be thrown if the user attempts to Update properties
that cannot be updated. For example, the following code will cause this warning
to be fired:
Customer1.GetByName("Joe Smith")
Customer1.Email = "joe@abc.com" 'ok
Customer1.CreditLimit = "200.00" 'Not used in Update operations!
Customer1.Update()
Only the email address will be updated, and the credit limit will be unchanged.
Each property description for entity objects lists whether or not it is used
in Update operations.
JournalLine Type
Debit or Credit line used in Journal Entries.
Syntax
InQBJournalLine (declared in inqb.h)
Remarks
Journal Lines are used to move funds from one account to another using the JournalEntry class, and can be used to represent both credits and debits.
- AccountId
- AccountName
- Amount
- BillableStatus
- ClassId
- ClassName
- EntityId
- EntityName
- LineId
- LineType
- Memo
- TaxItemId
- TaxItemName
Fields
AccountId
char*
Default Value: ""
The account for this line.
A reference to the account to be debited or credited. For example, "Checking".
Id/Name Reference Properties
This property is used to reference an object that is already done within QuickBooks. This may be done with its Id (this property) or its full Name, for which a corresponding property is defined.
Using the Id is recommended when feasible, as the Id is guaranteed to never change once defined.
Setting the value of this property will set the corresponding Name property to an empty string.
AccountName
char*
Default Value: ""
The account for this line.
A reference to the account to be debited or credited. For example, "Checking".
Id/Name Reference Properties
This property is used to reference an object that is already done within QuickBooks. This may be done with its Id (this property) or its full Name, for which a corresponding property is defined.
Using the Id is recommended when feasible, as the Id is guaranteed to never change once defined.
Setting the value of this property will set the corresponding Name property to an empty string.
Amount
char*
Default Value: ""
Amount of the debit or credit.
The total amount of this debit or credit line. Should be a positive number.
The amount should be formatted as a string in dollars.
BillableStatus
int
Default Value: 0
The billing status of this journal line.
If the billing status is empty (that is, if no billing status appears in QuickBooks), then BillableStatus will be bsEmpty
Values:
- bsEmpty (0)
- bsBillable (1)
- bsNotBillable (2)
- bsHasBeenBilled (3)
ClassId
char*
Default Value: ""
Class of the credit line.
A reference to the class of this debit or credit line. Used if class tracking is being done with the QuickBooks company.
Id/Name Reference Properties
This property is used to reference an object that is already done within QuickBooks. This may be done with its Id (this property) or its full Name, for which a corresponding property is defined.
Using the Id is recommended when feasible, as the Id is guaranteed to never change once defined.
Setting the value of this property will set the corresponding Name property to an empty string.
ClassName
char*
Default Value: ""
Class of the credit line.
A reference to the class of this debit or credit line. Used if class tracking is being done with the QuickBooks company.
Name/Id Reference Properties
This property is used to reference an object that is already done within QuickBooks. This may be done with its full Name (this property) or its Id, for which a corresponding property is defined. If Name is used, it must contain the full name of the object referred to, as generated by QuickBooks. For hierarchically defined objects, such as Customers, this includes the names of parent objects, and the full name can be determined by reading the FullName special field.
Setting the value of this property will set the corresponding Id property to an empty string.
EntityId
char*
Default Value: ""
An entity Id for this credit or debit line.
An Entity refers to a Customer, Vendor, Employee, or "Other Name" associated with this credit line. If AccountId/AccountName is an accounts receivable account, EntityName or EntityId should refer to a customer. If the account is an accounts payable account, Entity should refer to a vendor.
Id/Name Reference Properties
This property is used to reference an object that is already done within QuickBooks. This may be done with its Id (this property) or its full Name, for which a corresponding property is defined.
Using the Id is recommended when feasible, as the Id is guaranteed to never change once defined.
Setting the value of this property will set the corresponding Name property to an empty string.
EntityName
char*
Default Value: ""
An entity name for this credit or debit line.
An Entity refers to a Customer, Vendor, Employee, or "Other Name" associated with this credit line. If AccountId/AccountName is an accounts receivable account, EntityName or EntityId should refer to a customer. If the account is an accounts payable account, Entity should refer to a vendor.
Id/Name Reference Properties
This property is used to reference an object that is already done within QuickBooks. This may be done with its Id (this property) or its full Name, for which a corresponding property is defined.
Using the Id is recommended when feasible, as the Id is guaranteed to never change once defined.
Setting the value of this property will set the corresponding Name property to an empty string.
LineId
char*
Default Value: ""
Identification number of the Journal line, used for Updates.
If you need to add a new line in a transaction Update request, you can do so by setting the LineId to -1.
LineType
int
Default Value: 0
This field specifies whether the line is a Credit or Debit line. Possible values are:
0 (ltDebit - default) | A debit line. |
1 (ltCredit) | A credit line. |
TaxItemId
char*
Default Value: ""
A sales-tax item is used to calculate a single sales tax that is collected at a specified rate and paid to a single agency. A TaxItemId refers to an item on this list.
TaxItemName
char*
Default Value: ""
A sales-tax item is used to calculate a single sales tax that is collected at a specified rate and paid to a single agency. A TaxItemName refers to an item on this list.
Constructors
JournalLine()
InQBList Type
Syntax
InQBList<T> (declared in inqb.h)
Remarks
InQBList is a generic class that is used to hold a collection of objects of type T, where T is one of the custom types supported by the JournalEntry class.
Methods | |
GetCount |
This method returns the current size of the collection.
int GetCount() {}
|
SetCount |
This method sets the size of the collection. This method returns 0 if setting the size was successful; or -1 if the collection is ReadOnly. When adding additional objects to a collection call this method to specify the new size. Increasing the size of the collection preserves existing objects in the collection.
int SetCount(int count) {}
|
Get |
This method gets the item at the specified position. The index parameter specifies the index of the item in the collection. This method returns NULL if an invalid index is specified.
T* Get(int index) {}
|
Set |
This method sets the item at the specified position. The index parameter specifies the index of the item in the collection that is being set. This method returns -1 if an invalid index is specified. Note: Objects created using the new operator must be freed using the delete operator; they will not be automatically freed by the class.
T* Set(int index, T* value) {}
|
Config Settings (JournalEntry Class)
The class accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.JournalEntry Config Settings
A list of allowable AuthFlags is provided below.
"" or 0 | Do not send any auth flags |
0x01 | Support QB Simple Start |
0x02 | Support QB Pro |
0x04 | Support QB Premier |
0x08 | Support QB Enterprise |
0x80000000 | Force Auth Dialog |
To specify support for multiple editions, OR together the values for each edition.
NOTE: If the version of QuickBooks being used does not support AuthFlags, the contents of this config will be ignored. However, if QuickBooks does support this feature, setting "AuthFlags=1" (Support for Simple Start only) on a machine running QuickBooks 2013 Pro will result in an error message indicating that the Request Processor cannot be found.
A list of available values is provided below.
pdpOptional | Causes the QuickBooks authorization dialog to display a checkbox for user selection asking whether the user wants to allow the application to access personal data. |
pdpRequired | Causes the QuickBooks authorization dialog to not display the personal information checkbox for user selection, and instead display a warning that the application needs to access personal data. |
pdpNotNeeded | Causes the QuickBooks authorization dialog to not display the personal information checkbox for user selection, and instead display an informational message that the application will NOT access personal data. |
The default value is pdpOptional.
The following values are permitted:
0 | Don't Care |
1 | Single-User Mode |
2 | Multi-User Mode |
About Single-User and Multi-User Modes
If the connection to QuickBooks is made in single-user mode, QuickBooks will give exclusive access to the connecting application. It will lock out all other integrated applications; if QuickBooks and the company file are not already open in single-user mode by the QuickBooks user, the user will be locked out as well.
If the connection is made in multi-user mode, QuickBooks will allow all other integrated applications access. QuickBooks end users on other machines will also be allowed to access the file. However, if the application (rather than the end user) starts QuickBooks automatically, end users on the same machine will still be locked out.
If cmDontCare is specified, an appropriate connection mode will be chosen automatically. If a company file is open in either single-user or multi-user mode, the integrated application will accept that connection mode. If no company file is open, QuickBooks will login automatically in multi-user mode.
About Integrated and Automatic Login
Note that your application's login to QuickBooks might be either automatic or interactive. Interactive login is used when QuickBooks is already open. Access will be shared between the integrated application and the QuickBooks end user, and if multi-user mode is specified, other applications and users will have access as well. When a connection is made, QuickBooks will show a dialog window to the user, and ask the user if he/she wants to permit the connection.
Automatic login is used when QuickBooks is not already open. QuickBooks will be opened in the background, and will run until your application has finished its connection with QuickBooks. The QuickBooks user interface will not be displayed, and end-users on the same machine will be locked out. End-users on other machines, however, will be allowed access if multi-user mode is specified.
By default integrated applications do not have permission to login automatically. The first time an application interacts with QuickBooks, it must do so interactively, with QuickBooks and the company file open. The QuickBooks end user may then grant automatic login permission through Edit Preferences - Integrated Applications in the QuickBooks user interface. Click on the name of the application and then "Properties", and you may allow the application to login automatically.
For automatic login the CompanyFile must be specified. CompanyFile, ApplicationName, and other properties relating to the QuickBooks connection may be edited through QBConnectionString.
0 | The company file will accept the connection. This indicates that no company file is open, or the desired company file is already open. |
1 | The company file will not accept the connection. This indicates a different company file is already open. |
A query is submitted to QuickBooks when the value of this property is read. The empty string will be returned if no file is open, if QuickBooks is open in an access mode incompatible with QBConnectionMode, or if an error occurs.
If the value of this property is nonempty, the class may interact exclusively with the open file.
This is only necessary if using a self-signed certificate, or any other certificate that has not been signed by a Certificate Authority (CA) trusted by the system.
Reading the value of this setting will return an empty string.
A list of available values is provided below.
umpOptional | Causes the QuickBooks authorization dialog to display its default selections and let the user pick. Use this setting if you do not need unattended mode. |
umpRequired | Causes the QuickBooks authorization dialog to display only the selection choices of "No" (no authorization) or "Yes, allow access even if QuickBooks is not running" (authorize unattended mode). |
The default value is umpOptional.
Base Config Settings
The following is a list of valid code page identifiers:
Identifier | Name |
037 | IBM EBCDIC - U.S./Canada |
437 | OEM - United States |
500 | IBM EBCDIC - International |
708 | Arabic - ASMO 708 |
709 | Arabic - ASMO 449+, BCON V4 |
710 | Arabic - Transparent Arabic |
720 | Arabic - Transparent ASMO |
737 | OEM - Greek (formerly 437G) |
775 | OEM - Baltic |
850 | OEM - Multilingual Latin I |
852 | OEM - Latin II |
855 | OEM - Cyrillic (primarily Russian) |
857 | OEM - Turkish |
858 | OEM - Multilingual Latin I + Euro symbol |
860 | OEM - Portuguese |
861 | OEM - Icelandic |
862 | OEM - Hebrew |
863 | OEM - Canadian-French |
864 | OEM - Arabic |
865 | OEM - Nordic |
866 | OEM - Russian |
869 | OEM - Modern Greek |
870 | IBM EBCDIC - Multilingual/ROECE (Latin-2) |
874 | ANSI/OEM - Thai (same as 28605, ISO 8859-15) |
875 | IBM EBCDIC - Modern Greek |
932 | ANSI/OEM - Japanese, Shift-JIS |
936 | ANSI/OEM - Simplified Chinese (PRC, Singapore) |
949 | ANSI/OEM - Korean (Unified Hangul Code) |
950 | ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC) |
1026 | IBM EBCDIC - Turkish (Latin-5) |
1047 | IBM EBCDIC - Latin 1/Open System |
1140 | IBM EBCDIC - U.S./Canada (037 + Euro symbol) |
1141 | IBM EBCDIC - Germany (20273 + Euro symbol) |
1142 | IBM EBCDIC - Denmark/Norway (20277 + Euro symbol) |
1143 | IBM EBCDIC - Finland/Sweden (20278 + Euro symbol) |
1144 | IBM EBCDIC - Italy (20280 + Euro symbol) |
1145 | IBM EBCDIC - Latin America/Spain (20284 + Euro symbol) |
1146 | IBM EBCDIC - United Kingdom (20285 + Euro symbol) |
1147 | IBM EBCDIC - France (20297 + Euro symbol) |
1148 | IBM EBCDIC - International (500 + Euro symbol) |
1149 | IBM EBCDIC - Icelandic (20871 + Euro symbol) |
1200 | Unicode UCS-2 Little-Endian (BMP of ISO 10646) |
1201 | Unicode UCS-2 Big-Endian |
1250 | ANSI - Central European |
1251 | ANSI - Cyrillic |
1252 | ANSI - Latin I |
1253 | ANSI - Greek |
1254 | ANSI - Turkish |
1255 | ANSI - Hebrew |
1256 | ANSI - Arabic |
1257 | ANSI - Baltic |
1258 | ANSI/OEM - Vietnamese |
1361 | Korean (Johab) |
10000 | MAC - Roman |
10001 | MAC - Japanese |
10002 | MAC - Traditional Chinese (Big5) |
10003 | MAC - Korean |
10004 | MAC - Arabic |
10005 | MAC - Hebrew |
10006 | MAC - Greek I |
10007 | MAC - Cyrillic |
10008 | MAC - Simplified Chinese (GB 2312) |
10010 | MAC - Romania |
10017 | MAC - Ukraine |
10021 | MAC - Thai |
10029 | MAC - Latin II |
10079 | MAC - Icelandic |
10081 | MAC - Turkish |
10082 | MAC - Croatia |
12000 | Unicode UCS-4 Little-Endian |
12001 | Unicode UCS-4 Big-Endian |
20000 | CNS - Taiwan |
20001 | TCA - Taiwan |
20002 | Eten - Taiwan |
20003 | IBM5550 - Taiwan |
20004 | TeleText - Taiwan |
20005 | Wang - Taiwan |
20105 | IA5 IRV International Alphabet No. 5 (7-bit) |
20106 | IA5 German (7-bit) |
20107 | IA5 Swedish (7-bit) |
20108 | IA5 Norwegian (7-bit) |
20127 | US-ASCII (7-bit) |
20261 | T.61 |
20269 | ISO 6937 Non-Spacing Accent |
20273 | IBM EBCDIC - Germany |
20277 | IBM EBCDIC - Denmark/Norway |
20278 | IBM EBCDIC - Finland/Sweden |
20280 | IBM EBCDIC - Italy |
20284 | IBM EBCDIC - Latin America/Spain |
20285 | IBM EBCDIC - United Kingdom |
20290 | IBM EBCDIC - Japanese Katakana Extended |
20297 | IBM EBCDIC - France |
20420 | IBM EBCDIC - Arabic |
20423 | IBM EBCDIC - Greek |
20424 | IBM EBCDIC - Hebrew |
20833 | IBM EBCDIC - Korean Extended |
20838 | IBM EBCDIC - Thai |
20866 | Russian - KOI8-R |
20871 | IBM EBCDIC - Icelandic |
20880 | IBM EBCDIC - Cyrillic (Russian) |
20905 | IBM EBCDIC - Turkish |
20924 | IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol) |
20932 | JIS X 0208-1990 & 0121-1990 |
20936 | Simplified Chinese (GB2312) |
21025 | IBM EBCDIC - Cyrillic (Serbian, Bulgarian) |
21027 | Extended Alpha Lowercase |
21866 | Ukrainian (KOI8-U) |
28591 | ISO 8859-1 Latin I |
28592 | ISO 8859-2 Central Europe |
28593 | ISO 8859-3 Latin 3 |
28594 | ISO 8859-4 Baltic |
28595 | ISO 8859-5 Cyrillic |
28596 | ISO 8859-6 Arabic |
28597 | ISO 8859-7 Greek |
28598 | ISO 8859-8 Hebrew |
28599 | ISO 8859-9 Latin 5 |
28605 | ISO 8859-15 Latin 9 |
29001 | Europa 3 |
38598 | ISO 8859-8 Hebrew |
50220 | ISO 2022 Japanese with no halfwidth Katakana |
50221 | ISO 2022 Japanese with halfwidth Katakana |
50222 | ISO 2022 Japanese JIS X 0201-1989 |
50225 | ISO 2022 Korean |
50227 | ISO 2022 Simplified Chinese |
50229 | ISO 2022 Traditional Chinese |
50930 | Japanese (Katakana) Extended |
50931 | US/Canada and Japanese |
50933 | Korean Extended and Korean |
50935 | Simplified Chinese Extended and Simplified Chinese |
50936 | Simplified Chinese |
50937 | US/Canada and Traditional Chinese |
50939 | Japanese (Latin) Extended and Japanese |
51932 | EUC - Japanese |
51936 | EUC - Simplified Chinese |
51949 | EUC - Korean |
51950 | EUC - Traditional Chinese |
52936 | HZ-GB2312 Simplified Chinese |
54936 | Windows XP: GB18030 Simplified Chinese (4 Byte) |
57002 | ISCII Devanagari |
57003 | ISCII Bengali |
57004 | ISCII Tamil |
57005 | ISCII Telugu |
57006 | ISCII Assamese |
57007 | ISCII Oriya |
57008 | ISCII Kannada |
57009 | ISCII Malayalam |
57010 | ISCII Gujarati |
57011 | ISCII Punjabi |
65000 | Unicode UTF-7 |
65001 | Unicode UTF-8 |
Identifier | Name |
1 | ASCII |
2 | NEXTSTEP |
3 | JapaneseEUC |
4 | UTF8 |
5 | ISOLatin1 |
6 | Symbol |
7 | NonLossyASCII |
8 | ShiftJIS |
9 | ISOLatin2 |
10 | Unicode |
11 | WindowsCP1251 |
12 | WindowsCP1252 |
13 | WindowsCP1253 |
14 | WindowsCP1254 |
15 | WindowsCP1250 |
21 | ISO2022JP |
30 | MacOSRoman |
10 | UTF16String |
0x90000100 | UTF16BigEndian |
0x94000100 | UTF16LittleEndian |
0x8c000100 | UTF32String |
0x98000100 | UTF32BigEndian |
0x9c000100 | UTF32LittleEndian |
65536 | Proprietary |
- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.
This setting only works on these classes: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.
Setting this configuration setting to true tells the class to use the internal implementation instead of using the system security libraries.
On Windows, this setting is set to false by default. On Linux/macOS, this setting is set to true by default.
To use the system security libraries for Linux, OpenSSL support must be enabled. For more information on how to enable OpenSSL, please refer to the OpenSSL Notes section.
Trappable Errors (JournalEntry Class)
Error Handling (C++)
Call the GetLastErrorCode() method to obtain the last called method's result code; 0 indicates success, while a non-zero error code indicates that this method encountered an error during its execution. Known error codes are listed below. If an error occurs, the GetLastError() method can be called to retrieve the associated error message.
ErrorsThe following errors may be generated by the class. Note that frequently the error message will contain more specific information than what is listed here.
JournalEntry Errors
101 | String too long. |
103 | Invalid date format (YYYY-MM-DD is standard). |
104 | Invalid value for enumerated field. |
105 | Invalid integer. |
106 | Invalid dollar amount. |
107 | Invalid boolean value (must be 'true' or 'false'). |
108 | Invalid number. |
111 | Invalid special characters in string. |
112 | Invalid special field syntax. |
181 | Could not load certificate file. |
201 | Required field unspecified. |
211 | Unsupported field specified. |
301 | Array line count must be nonnegative. |
302 | Array index out of bounds. |
303 | Invalid field index. |
401 | Field not accessible as a special field. |
402 | Write access attempted of readonly field. |
403 | Read access attempted of writeonly field. |
421 | The object cannot be modified. |
511 | The QBRequestId has been previously used. Please generate a new one. |
601 | Could not access QuickBooks. |
602 | Could not open specified file. |
603 | The version of QuickBooks currently being used is not supported. |
604 | QuickBooks has not been installed properly. |
605 | The specified file was of an incorrect version. |
606 | Could not start QuickBooks. |
607 | QuickBooks is open in a mode different than the one requested. |
608 | QuickBooks cannot currently be accessed. |
609 | An application name must be specified. |
610 | A file name must be specified if one is not currently open in QuickBooks. |
611 | Access denied. |
612 | QuickBooks is busy and cannot open your application in the mode requested. |
699 | The connection to QuickBooks has failed for an unknown reason. |
702 | The object requested does not exist in QuickBooks. |
751 | Unsupported QBXML version. |
752 | The QBXMLVersion chosen is insufficient to execute the request. |
801 | A QuickBooks internal error has occurred. |
802 | QuickBooks is not available due to a system-related problem. |
803 | The Id specified is invalid. |
804 | Invalid object name. |
805 | The name already exists in QuickBooks. |
807 | An object could not be found in QuickBooks. |
808 | A reference did not refer to an object that exists in QuickBooks. |
809 | The object is currently in use by the QuickBooks end user. |
810 | The object may not be added. |
811 | The object may not be updated because it is obsolete. |
812 | The address is invalid. |
813 | Permission to perform this operation is not granted. |
814 | The request has not been processed. |
815 | Time creation mismatch. |
816 | The feature is turned off or not enabled. |
817 | Permission level configured is insufficient for access. |
818 | The item specified was of an unknown type. |
819 | The object may not be changed. |
820 | An internal QuickBooks error has occurred. |
821 | An attempt was made to use a connection that was not properly initiated. |
822 | An attempt was made to use a connection that is invalid or was previously closed. |
823 | Not enough memory. |
824 | Unable to lock the necessary information to allow this application access to the company file. Try again later. |
850 | An older version of QuickBooks 2002 is being used. Please download the latest update from Intuit. |
851 | The QuickBooks request processor was not found. Check that QuickBooks Pro 2002 or higher is installed on your system. |
861 | Server error on WebExport (details follow). |
862 | The WebExport is impossible: an HTTP context was not found. |
871 | You may not set the value of QBConnectionTicket. This value is readonly. |
880 | Interrupted by the user. |
881 | An error has occurred connecting to a remote machine. |
899 | An unknown QuickBooks error has occurred. The message contains more details. |
901 | XML Parser Error. Should not occur under normal circumstances. |